Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!genat!clunk!bvax!da
From: da@bvax.UUCP
Newsgroups: ont.uucp
Subject: Re: file D.siteA1234 can't access
Message-ID: <319@bvax.UUCP>
Date: Wed, 2-Dec-87 08:48:34 EST
Article-I.D.: bvax.319
Posted: Wed Dec  2 08:48:34 1987
Date-Received: Sat, 5-Dec-87 09:14:11 EST
References: <1987Nov30.235047.7349@lsuc.uucp>
Distribution: ont
Organization: Bell Canada, Toronto, CANADA
Lines: 20
Summary: S got fail

In article <1987Nov30.235047.7349@lsuc.uucp>, dave@lsuc.uucp (David Sherman) writes:
> (expected 'S' got FAIL), and FAILED (conversation complete),
> so maybe I'm just seeing the results of a flaky phone line or
> modem.  

We have been doing a lot of work with uucp in the last few months and have
found that if the system receiving the file is loaded down and the file
received is large the uucp will fail at times with the 'S' expected got
fail or some such message. 

The reason for this is when the file copy has been completed between machines,
the target machine must copy the temp file to the target directory. If the
system must copy from one sector to another or between drives and the system
is loaded uucp will timeout before this is completed. We found that a file
of 50K size always gets copied but files of 500K fail at times.

I don't know anything about the machine you are sending to, but I thought
I would pass this info along.

Dave Sellers