Path: utzoo!utgpu!water!watmath!clyde!ima!spdcc!dyer
From: dyer@spdcc.COM (Steve Dyer)
Newsgroups: comp.mail.uucp
Subject: Re: uucp via a rlogin session
Message-ID: <2003@spdcc.COM>
Date: 9 Oct 88 02:46:56 GMT
References: <531@comdesign.CDI.COM> <317@magnus.UUCP> <13797@mimsy.UUCP> <166@carpet.WLK.COM> <13811@mimsy.UUCP>
Reply-To: dyer@spdcc.COM (Steve Dyer)
Distribution: na
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Lines: 41

In article <13811@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
>As long as UUCP never transmits one of the sequences
>
>	RETURN escchar .
>	RETURN escchar Meta-DEL
>	RETURN escchar escchar
>
>(where escchar is the character set by -e, default `~') it will
>continue to work.  Obviously, these three sequences are statistically
>unlikely: P=3/256^3 in uniformly random data, or about .000018%.  You
>should be able to manufacture a file that will reliably break the
>connection, however, and Murphy dictates that your boss will do it.

I should mention that I've been UUCPing at 9600 baud using rlogin from
an annex box for over a year now.  I get all my news and mail this way.
This doesn't invalidate anything Chris says, but I've never come across
a file of any sort which was a "bottleneck" and hung things up until it
was deleted.  I will have to try his suggestion.

This works successfully with 4.3BSD on both VAXes and RT/PCs.
HOWEVER, I find that I am unable to reliably use this to any Ultrix
system--while UUCP transfers from the Ultrix machine to spdcc work
more or less OK, any transfers in the spdcc-->Ultrix direction ultimately
time out.  This occurs even with running 4.3BSD UUCP under Ultrix.
I had originally seen this only when trying to connect to machines
on the other end of a slow link (9600 baud) and thought it might 
result from the Annex's incorrect calculation of RTT and subsequent wasteful
retransmissions--I hadn't made the connection yet that it was happening
only with Ultrix machines.  However, I had the unfortunate experience of
finding my primary news feed which is on the same ethernet as the Annex
box converted overnight from 4.3BSD to Ultrix 2.2 and the same thing happens--
the rlogin sessions which had been working for so long were now effectively
useless.

Anyone know what's going on there?  I was thinking maybe DEC diddled
with their PTYs to handle DECnet better or their TCP/IP implementation
or something.  Suggestions or enlightenment welcome.
-- 
Steve Dyer
dyer@harvard.harvard.edu
dyer@spdcc.COM aka {harvard,husc6,linus,ima,bbn,m2c,mipseast}!spdcc!dyer