ssh & sftp terminal timeout
Chris G
cl at isbd.net
Wed Apr 25 21:05:28 UTC 2007
On Wed, Apr 25, 2007 at 10:32:46AM -0700, Wolfgang S. Rupprecht wrote:
>
> Chris G <cl at isbd.net> writes:
> > # Run ka (keep alive) if this is a remote ssh login
> > #
> > if [ "$SSH_CLIENT" ]
> > then ka&
> > fi
>
> Why not just turn on the ssh and sshd keep-alives?
>
Because on the version of ssh I was using when I did this these
parameters didn't exist!
> sshd_config:
> ClientAliveInterval 60
> ClientAliveCountMax 30
>
> ssh_config:
> ServerAliveInterval 60
> ServerAliveCountMax 30
>
> These settigns will send a packet every 60 seconds to keep the NAT
> state fresh when using a losing home NAT box (like the wrt54g when
> running factory firmware). As an added benefit after 30 minutes of
> dropped packets the program at each end exits.
>
> I used to have a problem with a buddy that had one of the above
> routers that would complain that my system's sshd dropped him after 10
> minutes of inactivity. I sent him a ps showing that he had 6 sshd's
> still active here waiting for his next input. After I added the
> sshd_config settings his connections stopped dropping.
>
> -wolfgang
> --
> Wolfgang S. Rupprecht http://www.wsrcc.com/wolfgang/
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
--
Chris Green
More information about the fedora-list
mailing list