Xref: utzoo comp.dcom.modems:2872 comp.sys.att:4688
Path: utzoo!utgpu!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!ucsdhub!cuuxun!cuuxb!mmengel
From: mmengel@cuuxb.ATT.COM (Marc W. Mengel)
Newsgroups: comp.dcom.modems,comp.sys.att
Subject: Re: Verbose modems (Re: MORE 6386 UUCP WOES)
Keywords: cu, Hayes Modem
Message-ID: <2174@cuuxb.ATT.COM>
Date: 7 Nov 88 21:38:33 GMT
References: <319@argon.UUCP> <2096@cuuxb.ATT.COM> <727@wsccs.UUCP> <889@vsi.COM> <758@wsccs.UUCP> <83@prapc2.UUCP>
Reply-To: mmengel@cuuxb.UUCP (Marc W. Mengel)
Organization: AT&T-DSD, System Engineering for Resellers, Lisle IL
Lines: 14


> In article <5042@cbmvax.UUCP>, ditto@cbmvax.UUCP (Michael "Ford" Ditto) writes:
> > I disagree.  Having "result codes" on a dialin modem on a Unix
> > system is a pretty stupid idea, for the above mentioned reason
> > (Modem sends "CONNECT" message to the computer ... computer thinks
> > "CONNECT" is a login name, etc.).

A good kluge for this particular problem is to make a login id called
"connect" with no password, and a login shell of /bin/false (or some
equally null program).  Then the "login" as CONNECT logs in that user
in upper case mode, but their login shell immediately exits...  The only
real problems there are if you have HUPCL set on the line, but make a
program that turns off HUPCL, then exits, and make that CONNECT's login shell,
and you're set.