Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!seismo!mcvax!cernvax!mebazf!bert
From: bert@mebazf.UUCP
Newsgroups: comp.unix.questions
Subject: uucico fails on call-in
Message-ID: <220@mebazf.UUCP>
Date: Sun, 22-Mar-87 18:59:59 EST
Article-I.D.: mebazf.220
Posted: Sun Mar 22 18:59:59 1987
Date-Received: Thu, 26-Mar-87 06:11:57 EST
Organization: Mettler AG Switz
Lines: 38

Hi there.

We have a problem here with our uucp system that has got me 
stumped.  We are running 4.3 BSD on a VAX 750.  The problem 
that we have is that incoming uucp calls seem to get fouled 
up unless we have local debug enabled.  The problem seems to 
be that the 'g' protocol gets out of sink between the two 
machines and we start getting 

    BAD READ (expected 'C' [or S or whatever] got FAIL (2))

messages in our LOGFILE.  This problem does not occur when 
we poll other systems, nor does it occur when our uucp login 
executes uucico with local debug on.  It also seems to depend 
on the 'strength' of the debugging level.  For instance, 
'uucico -x1' doesn't solve the problem, but '-x9' makes things 
run just dandy.

Other details :   

    - The problem occurs independent of whether the other system 
      is calling over a modem or is hard-wired with a direct 
      connection to our machine.

    - We didn't have any problems under 4.2 BSD.

    - The failure tends to happen early in the connection, 
      normally during the transfer of the first file from us to them.

Any solutions or suggestions would be greatly appreciated.


	  Thanks.

	    Bert Kay
	    Mettler Instrumente AG, CH-8606, Greifensee, Switzerland
	    ...ucbvax!mebazf!bert
	    ...mcvax!cernvax!unizh!mebazf!bert