LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 12-11-2000, 08:13 PM   #1
sshatz
LQ Newbie
 
Registered: Dec 2000
Location: New York City
Posts: 10

Rep: Reputation: 0
Question


One of my customers telnets into Red Hat Linux. I have noticed that periodically users are automatically disconnected from the server. I imagine this occurs when the user has been idle for too long. What I would like to know is in which file(s) the idle timeout is configured and if it is not specified, what is its default?

Today, a user locked up in Windows 98 while a telnet session to Linux was open on that PC. They powered their Windows PC off and on to reboot it. From log files, it looks like the telnet session finally terminated 2 hours later. Is this the idle timeout default?

I have searched the web and various books and can not find the information I seek. I would appreciate any help from the linuxquestions community.

Thank you.
 
Old 12-15-2000, 05:11 AM   #2
TK Tech
LQ Newbie
 
Registered: Dec 2000
Location: Cambodia
Posts: 8

Rep: Reputation: 0
Wink

I've heard the same problem which had happened to my friend too. He told me that to solve this is to set the time out both in TelNet configuration file and the user profile.

Let try...I've never done it, sorry....

Hope this gives you an idea.
 
Old 12-15-2000, 01:47 PM   #3
sshatz
LQ Newbie
 
Registered: Dec 2000
Location: New York City
Posts: 10

Original Poster
Rep: Reputation: 0
Thank you for responding. After a bit more research, I believe that I have a better understanding of what is happening. Users do not get disconnected just because they are idle for too long. When they are idle, the linux telnet process sends a KeepAlive signal to their PC. If the PC is still running, the client telnet process responds that it is there. This allows users to remain connected when they walk away from their PC, even overnight. (Not a great situation, but it doesn't appear to be problematic.)

Problems arise however, when a user reboots their PC (for whatever reason) while telnet'ed into the linux box. The same "idle too long"/KeepAlive process is followed, but since the client telnet session is no longer running, it can't respond and after a series of failed responses, the host telnet process kills the session. Unfortunately, the idle too long threshhold seems to be defaulting to 2 hours. Thus when this happens during the day, there can be a long wait before record locks and other settings are freed.

If we could identify idle, disconnected jobs, they could be killed, which would release the resources. But there is no one on site with that expertise. What I would like to do is find a way to reduce the 2 hour idle threshhold to say, 30 minutes.

Does anyone know which (if any) telnet configuration file and parameter would allow me to set this? Also, TK Tech, I don't understand which User Profile you are referring to? Do you mean a Windows User Profile or a linux .bashrc or .profile file? Of course, I would also be interested in other solutions to the problem. Thanks, again.


 
Old 12-15-2000, 09:35 PM   #4
TK Tech
LQ Newbie
 
Registered: Dec 2000
Location: Cambodia
Posts: 8

Rep: Reputation: 0
Thumbs up

Quote:
Originally posted by sshatz
Thank you for responding. After a bit more research, I believe that I have a better understanding of what is happening. Users do not get disconnected just because they are idle for too long. When they are idle, the linux telnet process sends a KeepAlive signal to their PC. If the PC is still running, the client telnet process responds that it is there. This allows users to remain connected when they walk away from their PC, even overnight. (Not a great situation, but it doesn't appear to be problematic.)

Problems arise however, when a user reboots their PC (for whatever reason) while telnet'ed into the linux box. The same "idle too long"/KeepAlive process is followed, but since the client telnet session is no longer running, it can't respond and after a series of failed responses, the host telnet process kills the session. Unfortunately, the idle too long threshhold seems to be defaulting to 2 hours. Thus when this happens during the day, there can be a long wait before record locks and other settings are freed.

If we could identify idle, disconnected jobs, they could be killed, which would release the resources. But there is no one on site with that expertise. What I would like to do is find a way to reduce the 2 hour idle threshhold to say, 30 minutes.
Well, good explanation for me, thanks.

Quote:
Does anyone know which (if any) telnet configuration file and parameter would allow me to set this? Also, TK Tech, I don't understand which User Profile you are referring to? Do you mean a Windows User Profile or a linux .bashrc or .profile file? Of course, I would also be interested in other solutions to the problem. Thanks, again.
As I've called my friend again, he said "the time out set in .bashrc of each user, this also can log out the user who is idling over the limited time out." Come on try it...

Good luck !

PS: Sorry, If my friend was at home I would ask him to help you, but he was on holiday. Telephoning in my sweetest country is v'ry expensive to my sal--y...
 
Old 05-22-2001, 10:58 AM   #5
jack_fr
LQ Newbie
 
Registered: May 2001
Posts: 1

Rep: Reputation: 0
[QUOTE]Originally posted by TK Tech
Quote:
If we could identify idle, disconnected jobs, they could be killed, which would release the resources. But there is no one on site with that expertise. What I would like to do is find a way to reduce the 2 hour idle threshhold to say, 30 minutes.
the default timeout for the session you're talking about is set in /proc/sys/net/ipv4/tcp_keepalive_time (on my system running SuSE 7.0).
The default value for this keepalive is 7200 seconds... simply edit the file and put the value you want (1800 in your case for a 30 minutes keepalive).

Hope this helps...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Red Hat 7 automatic partion doesn't work uffdakev Linux - Newbie 2 11-23-2003 09:31 PM
New installation of Red Hat 9 - automatic partitioning? BRFCclare Linux - Software 4 10-17-2003 09:37 AM
Telnet on Red Hat 8.0 SAW Linux - Networking 3 06-24-2003 03:07 AM
Red Hat 8.0 Telnet The_Master Linux - General 3 12-09-2002 05:01 PM
SHH and Telnet problems in Red Hat 8.0 The_Master Linux - Distributions 1 10-30-2002 02:08 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 05:28 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration