Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!swrinde!cs.utexas.edu!uunet!newsflash.concordia.ca!sifon!clouso.crim.ca!sobeco!zap!fortin From: fortin@zap.uniforum.qc.ca (Denis Fortin) Subject: Re: dial in (0.2.4) Organization: zap, Montreal, QC, Canada References: <21p7es$jf6@urmel.informatik.rwth-aachen.de> <CA7FKC.MIo@zap.uniforum.qc.ca> <1993Jul16.071001.23914@cnplss5.cnps.philips.nl> Message-ID: <CAGo7H.Iru@zap.uniforum.qc.ca> Keywords: pk0.2.4, CD, sio Date: Tue, 20 Jul 1993 11:35:24 GMT Lines: 20 In article <1993Jul16.071001.23914@cnplss5.cnps.philips.nl> rooij@bashful.isp.cft.philips.nl (Guido van Rooij) writes: >fortin@zap.uniforum.qc.ca (Denis Fortin) writes: > >>there is a "login" process running for user "login:", which seems to >>indicate that the BIDIR stuff might have a small flaw somewhere. >>(i.e. the uucico fails and goes away, but the DTR isn't dropped > >Indeed. I forgot to implement a 'hold DTR down for a minimum time' >like in cgd's driver. It's quite easy to solve and I'll do it soon. >(Note that you can set it in your modem too: there is a S-reg >that specifies after how many msec's of DTR, teh connection is closed.) Hmmm... My machine must be pretty fast because I don't even see the light blinking on DTR when uucico goes away ;-). Anyway, I'll try to look into my modem's manual. The best solution would probably be to patch the driver! Should you be too busy these days, just drop me a note and I'll do it. Denis, fortin@zap.uniforum.qc.ca