|
Are you logging in by telnet or ssh? I'm wondering if
your daemon is doing something funny with keepalive for some reason. Some
telnetd's do have an option to turn it off. Try a man in.telnetd or just
man telnetd to see if that's a possibility.
rfp
>>> [EMAIL PROTECTED] 01/30/04 02:37PM >>> Hi
Robert, Thanks
for the information�I�ve tried what you suggested. I modified the
tcp_keepalive_time, tcp_keepalive_intvl, and tcp_keepalive_probe settings. Below
is how they�re currently set�. [EMAIL PROTECTED]
/root]# more
/proc/sys/net/ipv4/tcp_keepalive_* :::::::::::::: /proc/sys/net/ipv4/tcp_keepalive_intvl :::::::::::::: 30 :::::::::::::: /proc/sys/net/ipv4/tcp_keepalive_probes :::::::::::::: 5 :::::::::::::: /proc/sys/net/ipv4/tcp_keepalive_time :::::::::::::: 60 I set
these up in the init script and rebooted the machine, verified that they were
still in place and then did the whole connect / unplug cable / reconnect cable
bit. Based on
these settings, I would have thought that after 60 seconds of inactivity, that I
would get a max of 5 probes at 30 second intervals, and if no response was
received, the connection would die.
That should be a total of�60 seconds + (30 seconds * 5 tries = 150) = 210
seconds or just under 4 minutes� However,
I�ve been back in for about 15 minutes now, and still see both logins when I do
the who�. Did I
miss something? Thanks, Donnie Jacobs Sr
Developer GC Services
LP 713-776-6503 -----Original
Message----- That's a TCP/IP
keepalive timeout... The
setting is viewable and changable - It should be found at
/proc/sys/net/ipv4/tcp_keepalive_time Changing
it won't survive a reboot though. You'll either need to change it every time or
do so in a script at init. rfp
|
_______________________________________________ u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
