Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!sequoia!ultima!kralizec.zeta.org.au!kralizec.zeta.org.au!not-for-mail From: bde@kralizec.zeta.org.au (Bruce Evans) Newsgroups: comp.os.386bsd.questions Subject: Re: sio - problem with login hanging up Date: 2 Aug 1993 00:14:07 +1000 Organization: Kralizec Dialup Unix Sydney: +61-2-837-1183 V.32bis Lines: 20 Message-ID: <23gj3fINNj7s@kralizec.zeta.org.au> References: <CAq3uA.9nx@sugar.NeoSoft.COM> <231ka4INNrkf@kralizec.zeta.org.au> <1993Jul27.190228.22230@emba.uvm.edu> <CAuGp4.ALD@sugar.NeoSoft.COM> NNTP-Posting-Host: kralizec.zeta.org.au In <CAuGp4.ALD@sugar.NeoSoft.COM> peter@NeoSoft.com (Peter da Silva) writes: >To BDE: >As for clocal, a terminal can easily be wired so it doesn't matter if >you're clocal or not. A modem, you really should default to -clocal, >and you can't wire it. I think the default should therefor be -clocal. I'm going to make -clocal the default for dialin ports and clocal the default for dialout ports. Dialout ports will always be enabled - no COM_BIDIR or comcontrol; you can restrict access to or delete unwanted dialout or dialin devices. I think clocal is right for dialout because no-carrier is the normal state before a connection has been established and between connections. Clocal is now ignored when dialout ports are opened so that they can be opened before carrier is present. Clocal is NOT ignored when the modem hangs up and this prevents multiple dialouts if clocal is clear. -- Bruce Evans bde@kralizec.zeta.org.au