Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site nsc-pdc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!tektronix!reed!nsc-pdc!joemu
From: joemu@nsc-pdc.UUCP (Joe Mueller)
Newsgroups: net.bugs.uucp
Subject: 4.2 uucp bug?
Message-ID: <226@nsc-pdc.UUCP>
Date: Tue, 9-Jul-85 01:24:58 EDT
Article-I.D.: nsc-pdc.226
Posted: Tue Jul  9 01:24:58 1985
Date-Received: Thu, 11-Jul-85 20:20:56 EDT
Distribution: net
Organization: NSC Portland Development Center, Portland Oregon
Lines: 11

[eat me]

Since I received such incredibly useful information regarding another bug
I had in uucp I thought that I'd see if anyone else has seen this problem.
When I look in LOGFILE I see the "OK (conversation complete)" message followed
by a "TIMEOUT (machine-name)" message. It looks like our 4.2 BSD machine is
missing the "OOOOO" message from the other machine. It's not a fatal problem
since the transfer has already completed and it hangs up after the timeout,
it's just a nusance that I'd like to remove. If I figure out the problem or
someone gives me the solution and there is sufficient interest, I'll post the
fix. Any leads would be greatly appreciated.