Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!psuvax1!burdvax!sdcrdcf!otto!jimi!johnny!robert
From: robert@johnny.cs.unlv.edu (Robert Cray)
Newsgroups: comp.unix.wizards
Subject: Re: 60-second timeout in Unix login
Message-ID: <720@jimi.cs.unlv.edu>
Date: Mon, 23-Nov-87 23:57:42 EST
Article-I.D.: jimi.720
Posted: Mon Nov 23 23:57:42 1987
Date-Received: Fri, 27-Nov-87 23:08:48 EST
References: <4139@venera.isi.edu> <3516@xanth.UUCP>
Sender: news@jimi.cs.unlv.edu
Reply-To: robert@jimi.cs.unlv.edu (Robert Cray)
Organization: University of Nevada, Las Vegas
Lines: 19

In article <3516@xanth.UUCP> kyle@xanth.UUCP (Kyle Jones) writes:
>In article <4139@venera.isi.edu>, cracraft@venera.isi.edu (Stuart Cracraft) writes:
>> The 60-second timeout in Unix login is not long enough.
>> 
>If the network between the local host and the remote host is so
>clogged that you can't get your login name and password to remote
>machine within 60 seconds, you certainly shouldn't be loading the net
>any further.  And you weren't going to get much done until the network
>activity died down, anyway.

Often its not a case of getting a lot done, but getting just a little done,
perhaps making a single change in a file, creating a directory or some such.
This is usually the case for me when I end up on a slow network link to do
something.  Also, the net may not be overly loaded -- I go via decnet across
the country through 3 links, then telnet to the unix machine.  In and of
themselves the links are not overloaded, but combined they tend to make
things a bit slow...

						--robert