Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site mtuxn.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!whuxlm!whuxl!houxm!mtuxo!mtuxn!rubin
From: rubin@mtuxn.UUCP (M.RUBIN)
Newsgroups: net.bugs.uucp
Subject: Direct uucp links on 3B2's
Message-ID: <584@mtuxn.UUCP>
Date: Fri, 12-Jul-85 20:47:10 EDT
Article-I.D.: mtuxn.584
Posted: Fri Jul 12 20:47:10 1985
Date-Received: Sat, 13-Jul-85 14:36:08 EDT
Organization: AT&T Information Systems, Holmdel NJ
Lines: 22

We found that uucp between two 3B2's (running SYSV.2 and HoneyDanBer uucp)
over a direct line was taking a long time (30-60 sec.) to start talking.  
Turns out the entry in the Systems file, which we had written according to the
dimwits' documentation that comes with the 3B2 (and would have been written
for us by the Simple Administration program that comes with the 3B2), went:

	othersys Any othersys 9600 - in:--in: n\pu\pu\pc\pp

Unfortunately, the uugetty at the other end requires a return before it
will say "login:", and since our machine was waiting for the "login:"
nothing happened until uugetty hit a 60-second timeout.  The above entry
could only work with getty at the other end, not uugetty, i.e. a one-way
line.  At any rate, the CORRECT entry in Systems is:

	othersys Any othersys 19200 - "" \r in:--in: n\pu\pu\pc\pp

Note the pauses in between "nuucp"; login can't handle 19200 baud input!
(We also found no problems using 19200 baud instead of the recommended
9600.  Then again we're using a very short cable.)

--Mike Rubin, AT&T Information Systems, Freehold NJ
		{ihnp4, rest of AT&T}!mtuxn!newtech!rubin