On 5/18/06, Andrew Lentvorski <[EMAIL PROTECTED]> wrote:
Carl Lowenstein wrote:
> Frequently I log in by ssh to a remote computer. If I don't keep
> using the connection, after a few minutes I get the message
> " Read from remote host deeptow: Connection reset by peer
> Connection to deeptow closed."
Are you sure this is an ssh/sshd issue?
Quite often this is a login shell issue.
The evidence I have is that I can remain logged in and idle for weeks
at a time as a local user. The "Connection reset" happens only when I
use ssh from another site. For what it's worth, the login shell is:
deeptow: cdl 506$ bash --version
GNU bash, version 2.05a.0(1)-release (alpha-unknown-linux-gnu)
Perusal of $(man bash) shows:
TMOUT If set to a value greater than zero, the value is
interpreted as the number of seconds to wait for
input after issuing the primary prompt. Bash ter-
minates after waiting for that number of seconds if
input does not arrive.
But $TMOUT is not set in my environment on the remote machine in any
way that I can detect. A small local experiment, starting another
instance of bash and setting TMOUT:
[EMAIL PROTECTED] tmp]$ bash
[EMAIL PROTECTED] tmp]$ export TMOUT=10
[EMAIL PROTECTED] tmp]$ timed out waiting for input: auto-logout
So indeed TMOUT works. But the message is different.
I will ask the networking people where the remote machine resides
whether they have done anything with their switch setup that might
disconnect idle users.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
