[uu]getty running you'll OBM will answer (was Re: UNIXPC uucp problem)

[Lenny Tropiano]

In article <3915 at cbterra.ATT.COM> mhm at cbterra.ATT.COM (Mike H. Moran) writes:
|>In article <382 at manta.UUCP>, brant at manta.UUCP (Brant Cheikes) writes:
|>> In article <103 at cjsa.UUCP> jeff at cjsa.UUCP (C. Jeffery Small) writes:
|>> >In article <1988Jun27.202651.9458 at ziebmef.uucp>, becker at ziebmef.uucp writes:
|>
|>[ much stuff about inittab enteries, etc ....]
|>
|>> This puts a uugetty on the phone line waiting for an incoming
|>> connection.  I believe the getty initializes the port to answer
|>> incoming calls.  You may need to replace /usr/lib/uucp/uugetty above
|>> with /etc/getty.  Without a getty, your machine won't answer.
|>
|>Not quite true, uugetty is supposed to be intelligent :-) in that it
|>will answer incomming calls as well as allow out going calls on the
|>same port without need of inittab modfication.
|>
|>Mike Moran 
|>Contracted to AT&T-BL			UUCP:  att!cbosgd!mhm
|>Columbus, Ohio				       mhm at cbosgd.att.com  

What Brant was trying to say that the /usr/lib/uucp/uugetty line that he used
as an example should be replaced with /etc/getty for those not running HDB.
While it is true that uugetty allows bi-directional traffic without turning
off the "getty", Brant's comment about "Without a getty, your machine
won't answer" still stands.  If the [uu]getty isn't "respawn"ing, then your
phone won't answer, the essence of the original subject and news article.

-Lenny
-- 
Paper-net: Lenny Tropiano          | @-net:         lenny at icus.UUCP
           ICUS Software Systems   | !-net:      ...att    \
           PO Box 1                |                boulder \
           Islip Terrace, NY 11752 |                talcott  !icus!lenny
Vocal-net: (516) 582-5525 [work]   |                pacbell /
           (516) 968-8576 [home]   |                sbcs   /
Telex-net: 154232428 ICUS          | Another-net:   attmail!icus!lenny