Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!killer!vector!rpp386!jfh From: jfh@rpp386.Dallas.TX.US (The Beach Bum) Newsgroups: comp.unix.wizards Subject: Re: vhangup Summary: why not just close the file? Message-ID: <9124@rpp386.Dallas.TX.US> Date: 4 Dec 88 21:11:00 GMT References: <13@cmdfs2.intel.com> <2246@bucsb.UUCP> <5197@mit-vax.LCS.MIT.EDU> Reply-To: jfh@rpp386.Dallas.TX.US (The Beach Bum) Organization: Big "D" Home for Wayward Hackers Lines: 13 In article <5197@mit-vax.LCS.MIT.EDU> keith@expo.lcs.mit.edu (Keith Packard) writes: >Admittedly, the vhangup code in 4.3 is terrible. But, it can be made very >useful. The current code turns off read/write bits in the file table. A >big mistake, as the file remains "open", which causes the carrier to remain >up and other problems. Why can't the file just be closed? Why wasn't this done? How come I wasn't consulted ;-) ? -- John F. Haugh II +-Cat of the Week:--------------_ /|- VoiceNet: (214) 250-3311 Data: -6272 |Aren't you absolutely sick and \'o.O' InterNet: jfh@rpp386.Dallas.TX.US |tired of looking at these damn =(___)= UucpNet :!killer!rpp386!jfh +things in everybody's .sig?-------U---