Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!cwruecmp!nitrex!rbl
From: rbl@nitrex.UUCP
Newsgroups: comp.sources.d
Subject: Re: modem: a bi-directional uucp port controller
Message-ID: <414@nitrex.UUCP>
Date: Sat, 31-Jan-87 12:03:11 EST
Article-I.D.: nitrex.414
Posted: Sat Jan 31 12:03:11 1987
Date-Received: Sat, 31-Jan-87 20:01:28 EST
References: <4474@robin.cs.nott.ac.uk> <586@sask.UUCP> <357@apc3b2.UUCP>
Reply-To: rbl@nitrex.UUCP ( Dr. Robin Lake )
Organization: The Standard Oil Co., Cleveland
Lines: 30
Keywords: uugetty, 3B, ATT
Summary: Another uugetty problem

In:
Message-ID: <357@apc3b2.UUCP>


Jon notes:
>In article <586@sask.UUCP>, coleman@sask.UUCP (Geoff Coleman) writes:
>> 
>> The version of UUCP I got with our 3b2/400 comes with a replavement for getty
>> called ugetty. Don't all Sys V distributions have this.
>
>All 3Bx will have uugetty.  Warning though about shutdown.  You have to
>modify the order of files in shutdown.d to kill the uugettys LAST (I think,
>I don't use it anymore).  It also has had some problems with spurious garbage
>tying up the system (except for the console).  Not a nice thing to do.
>
>-- 

Also, if uugetty is running on a 3B serial port, someone coming into that
port will have to try twice.  The first time, uugetty "turns itself around"
for incoming service.  The second time, it connects.

If you have a long access sequence to get thru data switches, access control
passwords, networks, etc., this CAN be a pain.  Particularly if the uugetty
decides to "turn itself back" into an outgoing port before you can access
it again.  Of course, if you have an access method that may connect you to
a different port on the next call in, it's become a neat game ....

Rob Lake
decvax!cwruecmp!nitrex!rbl
ihnp4!{cbatt,cbosgd}!nitrex!rbl