hi ! have you tried playing with the ssh-configs?
like in /etc/ssh/sshd_config KeepAlive yes from the man page # KeepAlive # Specifies whether the system should send TCP keepalive messages # to the other side. If they are sent, death of the connection or # crash of one of the machines will be properly noticed. However, # this means that connections will die if the route is down tem- # porarily, and some people find it annoying. On the other hand, # if keepalives are not sent, sessions may hang indefinitely on the # server, leaving ``ghost'' users and consuming server resources. # The default is ``yes'' (to send keepalives), and the server will # notice if the network goes down or the client host crashes. This # avoids infinitely hanging sessions. # To disable keepalives, the value should be set to ``no''. This option is also available in $HOME/.ssh/config and /etc/ssh/ssh_config I use this and it works (and "keepalive's" only ssh) if you want to use your tcp_keepalive_time, why don't you put it into /etc/conf.d/local.start ? (check if you neet to "rc-update add local default") Joe On Tuesday 25 March 2003 22:04, gabriel wrote: > i finally found out what was causing remote servers to kick me out of an > ssh session after a long (a few minutes) period of inactivity. the > "keepalive" interval time in my kernel was long, so it wasn't stimulating > the server often enough to keep the connection open. > > a soloution i found w/ google's help was the following: > > echo 300 > /proc/sys/net/ipv4/tcp_keepalive_time > > works like a charm, but every time i reboot my box, the original value of > 7200 returns and i have to run that little line again. is there a more > efficient way to do this? -- [EMAIL PROTECTED] mailing list
