Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1a 12/4/83; site rlgvax.UUCP
Path: utzoo!linus!decvax!harpo!seismo!rlgvax!guy
From: guy@rlgvax.UUCP (Guy Harris)
Newsgroups: net.bugs.uucp,net.mail,net.flame
Subject: Re: BUG in System III [and others] UUCP (FLAME)
Message-ID: <1549@rlgvax.UUCP>
Date: Sat, 14-Jan-84 15:59:08 EST
Article-I.D.: rlgvax.1549
Posted: Sat Jan 14 15:59:08 1984
Date-Received: Sun, 15-Jan-84 06:01:05 EST
References: <205@dual.UUCP> <4575@umcp-cs.UUCP>
Organization: CCI Office Systems Group, Reston, VA
Lines: 14

The "gio.c" that comes with the 4.2BSD UUCP does do this checking; however,
be warned that the routine above it doesn't do anything pleasant with the
error return.  It just says "oops, something failed, the h*ll with it" and
terminates the entire UUCP session, so if a file is too big for the file
system the spool directory is on (or exceeds the "ulimit" maximum file size
on USG systems), or gets a write error, or if a file being sent has a bad
block in it, the UUCP session will terminate with no more meaningful
diagnostics than "FAILED (conversation complete)".  It *does* get caught,
but doesn't get reported properly back to the user at all (and would take
a bit of jerking the code around to do so, which is probably why it wasn't
done).

	Guy Harris
	{seismo,ihnp4,allegra}!rlgvax!guy