Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site onfcanim.UUCP
Path: utzoo!watmath!water!watcgl!onfcanim!dave
From: dave@onfcanim.UUCP (Dave Martindale)
Newsgroups: net.news
Subject: Re: uucico timing out
Message-ID: <14686@onfcanim.UUCP>
Date: Wed, 11-Sep-85 21:51:28 EDT
Article-I.D.: onfcanim.14686
Posted: Wed Sep 11 21:51:28 1985
Date-Received: Thu, 12-Sep-85 08:57:02 EDT
References: <383@greipa.UUCP>
Reply-To: dave@onfcanim.UUCP (Dave Martindale)
Distribution: net
Organization: ONF, Montreal
Lines: 22

In article <383@greipa.UUCP> paul@greipa.UUCP (Paul A. Vixie) writes:
>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.
>

Is this a timeout during the conversation, or after it is complete?

There is a bug in (some versions of, at least) system V uucp that causes
it not to send the final OOOOO message properly, and the machine on the
other end (at least if it's a Berkeley unix) eventually times out.
The symptoms of this are that the log file shows CONVERSATION COMPLETE
before the TIMEOUT.  If this is what is happening to you, don't worry
about it - everything is in fact getting through.

However, if it is happening during the conversation, you probably have
a noise line and the modems eventually drop carrier.  Nothing should
be lost, but this can badly degrade the amount of stuff transferred
over that connection.  The best fix is to fix the modem or phone line
or whatever is causing the problem.  To increase the timeout, you need
to have source for uucico (or a lot of skill with adb).  But if you
are really timing out, something is very unhealthy elsewhere.