Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!mit-eddie!allegra!mp From: mp@allegra.UUCP Newsgroups: comp.unix.wizards,comp.unix.questions Subject: Re: Modem hangup difficulties under 4.3BSD on a VAX Message-ID: <6596@allegra.UUCP> Date: Sun, 12-Apr-87 08:20:25 EST Article-I.D.: allegra.6596 Posted: Sun Apr 12 08:20:25 1987 Date-Received: Mon, 13-Apr-87 23:40:14 EST References: <4183@nsc.nsc.com> <29@sdeggo.UUCP> Organization: AT&T Bell Laboratories, Murray Hill Lines: 32 Xref: utgpu comp.unix.wizards:1748 comp.unix.questions:1688 In article <29@sdeggo.UUCP>, David Smith writes: > It's because the modem lines only get > dropped when the *last* close (i.e. everything which has the port open > closes it) is done. As long as you have a background process running > it still has the port open, unless you disassociate it from the port > somehow. Our problem is getting the modem to behave correctly after the last process is done. This system (4.2bsd 750) has one dialup, a Ventel 1.something (we've tried several, a few 1.11's and the newer tan things) on a dz. That tty is used only for uucp. The problem we have is that sometimes the modem will keep the phone line off-hook INDEFINITELY. It seems to happen most often when the system that has just called us has an entry near the bottom of our Systems file, or isn't listed in it at all. In these cases, I imagine uuxqt takes awhile to run, even when there's nothing to xqt (the sites who actually call us turn out not to be high-volume sites). The way I currently unwedge things manually is to disable the tty in /etc/ttys, kill -1 1, pause 15 seconds, re-enable the tty, and kill -1 1. Or I press a button on the Ventel to reset it. I suppose I could have uucico do a TIOCNOTTY before the exec of uuxqt. It already looks like it's closing all its file descriptors. I dimly remember a long time ago that someone said that adding a sleep(5) in init would fix things. Does anyone remember this? Mark Plotnick allegra!mp