Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp
Path: utzoo!linus!decvax!decwrl!sun!guy
From: guy@sun.uucp (Guy Harris)
Newsgroups: net.news
Subject: Re: uucico timing out
Message-ID: <2785@sun.uucp>
Date: Wed, 11-Sep-85 01:46:35 EDT
Article-I.D.: sun.2785
Posted: Wed Sep 11 01:46:35 1985
Date-Received: Thu, 12-Sep-85 23:25:36 EDT
References: <383@greipa.UUCP>
Distribution: net
Organization: Sun Microsystems, Inc.
Lines: 27

> I think my system is a bit to touchy on the timing - uusnap shows every
> system that we talk to as "TIMEOUT" and has for some time.  Systems log
> in and get an hour or two of news, then TIMEOUT.

Does it time out in the middle of a transfer, or does it successfully
complete a UUCP session?  Check the LOGFILE - if there's a message like

	<the other system> <log file crud> OK (conversation complete)


just before the timeout for that system, the timeout is only a timeout in
the hangup sequence.  There's a bug that's been in UUCP since time
immemorial, but which was only noticed in the 4.2BSD UUCP because other
UUCPs didn't bother making any note of timeouts like that.  Basically, the
protocol is incorrectly implemented, so one side waits for an extra
handshaking message that the other side has no intention of sending.  The
4.3BSD UUCP fixes this by not waiting for the extra message.  I suspect
honey danber does also (Peter?).  The bug is annoying but, as far as I know,
harmless.

> Of course there is no man page for uucico, so if there is an option for
> specifying the time limit I can't find it.  Any ideas, anyone?

Since this timeout is an internal protocol timeout, it is not
user-specifiable.

	Guy Harris