Path: utzoo!mnetor!uunet!husc6!uwvax!oddjob!gargoyle!ihnp4!occrsh!occrsh.ATT.COM!rjd
From: rjd@occrsh.ATT.COM
Newsgroups: comp.sys.att
Subject: Re: HDB UUCP fails on AT&T 3B2/310
Message-ID: <144800005@occrsh.ATT.COM>
Date: 22 Dec 87 17:06:00 GMT
References: <75@quincy.UUCP>
Lines: 23
Nf-ID: #R:quincy.UUCP:-7500:occrsh.ATT.COM:144800005:000:1097
Nf-From: occrsh.ATT.COM!rjd    Dec 22 11:06:00 1987


>> Has anyone else experienced problems with HoneyDanBer UUCP running on
>> an AT&T 3B2/310, Version 3.0 of the operating system?  I have noticed
>> the following quite frequently:
>> 	1.	Sending compressed binaries (16-bit compression) with
>> 		Penril modem 8216 from an AT&T 3B2 to another AT&T 3B2
>> 		long distance, I receive the imfamous:
>> 			CONVERSATION FAILED 
>> 			IN SEND/SLAVE MODE INPUT FAILURE
>
>I only have seen this litle goodie pop up on our 3b2's when the
>size of the file being sent exceeds the ulimit of that allowed
>for the login 'nuucp' or whatever is being sent..........

   I have also seen it happen for another (really same) reason: disk file space
(df command) on the receiving end's /usr filesystem gets used up.  This instance
is hard to catch, because as soon as the conversation fails, the temporary file
in /usr/spool/uucp/machine-name is removed, and disk space returns to a
non-critical value (though it is obviously already under a few hundred blocks).
   This explanation may not explain it though, as it should fail on the longer
file also.....

Randy