Re: Keeping SSH connections open

• Previous message: Darren Dunham: "Re: Keeping SSH connections open"
• In reply to: Darren Dunham: "Re: Keeping SSH connections open"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Date: Thu, 16 Jun 2005 18:35:03 GMT

On Thu, 16 Jun 2005 18:07:43 +0000, Darren Dunham wrote:

> Augustus SFX van Dusen <ASFXvD@story.net> wrote:
>> OK, I suspended box B, and the sshd processes in A associated with ssh
>> connections started in B died after less than 40 minutes, but after more
>> than 2 minutes. Whatever the actual value, it anyway is much lower than it
>> should be, if the
>
>> KeepAlive no
>> ClientAliveInterval 60
>> ClientAliveCountMax 600
>
>> lines in the sshd configuration file on A did what one would have expected.
>
>> So, what am I doing wrong?
>
> Can anything be displayed onto the shell during that time (mail
> notifications? Alerts? ..)

        Not that I know of. Under ordinary circumstances, if no typing is done
into those shells they just sit there forever waiting for input.
 

> My understanding is that those numbers are only true for idle
> connections. If actual data is trying to be delivered, it may timeout
> more quickly.
>
> I haven't looked at this in a *long* time, but I used to have a system
> on the other end of dialup that I wanted to maintain the connections
> overnight with the down modem. Some of those timeout settings weren't
> present back then.

• Previous message: Darren Dunham: "Re: Keeping SSH connections open"
• In reply to: Darren Dunham: "Re: Keeping SSH connections open"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]