Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/3/84; site lsrhs.UUCP
Path: utzoo!linus!decvax!genrad!grkermi!lsrhs!smiles
From: smiles@lsrhs.UUCP (Kevin "Mr. Boots" Ruddy)
Newsgroups: net.bugs.uucp
Subject: (maybe) problem with 4.2 packet driver
Message-ID: <808@lsrhs.UUCP>
Date: Mon, 6-Jan-86 15:03:20 EST
Article-I.D.: lsrhs.808
Posted: Mon Jan  6 15:03:20 1986
Date-Received: Tue, 7-Jan-86 06:55:53 EST
Expires: Thu, 6-Feb-86 00:00:00 EST
Reply-To: smiles@lsrhs.UUCP (Kevin "Mr. Boots" Ruddy)
Distribution: net
Organization: LSRHS, Sudbury MA
Lines: 11
Keywords: uucp, uucico

Is there some problem with the vanilla versions of this?  We frequently
have errors which look like this in .../LOG/uucico:

grkermit grkermit (1/6-13:47-14295) REQUESTED (S D.grkermib03oU D.grkermib03oU root)
root grkermit (1/6-13:50-14295) pkclose rcheck != p_rwindow (PK0)
root grkermit (1/6-13:50-14295) FAILED (conversation complete)

Sometimes, pkclose() doesn't print that message.  This happens at any point
during the transmission of this file, anywhere from between two minutes of
transmission and six.  We have not located the problem and wondered if the
net had any solutions.

Although this may not be the packet driver's fault, what could cause uucico
to fail consistently on the same file?
--
ADDR: Kevin Ruddy, 42 Pantry Road, Sudbury MA  01776
UUCP: {genrad!grkermit,harvard!wjh12,bbncca,mit-eddie!frog}!lsrhs!smiles
ARPA: lsrhs!smiles@bbncca.arpa