HPE GreenLake Administration
- Community Home
 - >
 - Servers and Operating Systems
 - >
 - Operating Systems
 - >
 - Operating System - HP-UX
 - >
 - Timeouts with Telnet
 
Operating System - HP-UX
        1840131
        Members
    
    
        2478
        Online
    
    
        110161
        Solutions
    
Forums
        Categories
Company
Local Language
                
                  
                  back
                
        
                
        
                
        
                
        
        
        
                
        
                
        
        
        
                
        
              
              Forums
Discussions
Forums
- Data Protection and Retention
 - Entry Storage Systems
 - Legacy
 - Midrange and Enterprise Storage
 - Storage Networking
 - HPE Nimble Storage
 
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
                
                  
                  back
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
            
                
            
                
            
                
            
                
            
            
                
            
                
            
            
                
            
                
              
            Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
 - Appliance Servers
 - Alpha Servers
 - BackOffice Products
 - Internet Products
 - HPE 9000 and HPE e3000 Servers
 - Networking
 - Netservers
 - Secure OS Software for Linux
 - Server Management (Insight Manager 7)
 - Windows Server 2003
 - Operating System - Tru64 Unix
 - ProLiant Deployment and Provisioning
 - Linux-Based Community / Regional
 - Microsoft System Center Integration
 
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
        Information
        Community
Resources
Community Language
        Language
        Forums
Blogs
	
		
			
            
                
            Go to solution
        
            
		
		
			
            	
	
		
        
		
	
	
		Topic Options
			
				
					
	
			
		
	- Subscribe to RSS Feed
 - Mark Topic as New
 - Mark Topic as Read
 - Float this Topic for Current User
 - Bookmark
 - Subscribe
 - Printer Friendly Page
 
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
02-28-2001 09:28 PM
02-28-2001 09:28 PM
			
				
					
					
						I know this is a stupid question, but does anyone know where you'd set an idle timeout on a telnet session?
thanks in advance.
Scott.
	
			
				
		
			
			
			
			
			
			
		
		
		
	
	
	
thanks in advance.
Scott.
Solved! Go to Solution.
		2 REPLIES 2
	
	            
            
		
		
			
            
                - Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
02-28-2001 09:32 PM
02-28-2001 09:32 PM
			
				
					
						
							Re: Timeouts with Telnet
						
					
					
				
			
		
	
			
	
	
	
	
	
			
				
					
					
						Hi,
Use the environment variable TMOUT. You can set it either in
1) /etc/profile
2) $HOME/.profile (for sh, bash, ksh shells)
3) $HOME/.cshrc or $HOME/.login (for csh, tcsh shells)
For 2), export TMOUT=600 (for 600 seconds or 10 mins)
For 3), setenv TMOUT 600
Hope this helps. Regards.
Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com
					
				
			
			
				
			
			
				
			
			
			
			
			
			
		
		
		
	
	
	
Use the environment variable TMOUT. You can set it either in
1) /etc/profile
2) $HOME/.profile (for sh, bash, ksh shells)
3) $HOME/.cshrc or $HOME/.login (for csh, tcsh shells)
For 2), export TMOUT=600 (for 600 seconds or 10 mins)
For 3), setenv TMOUT 600
Hope this helps. Regards.
Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
03-01-2001 05:15 AM
03-01-2001 05:15 AM
Solution
			
				
					
					
						Actually, the shell timeout in csh is called autologout.  Nothing in csh is compatible with anything else.  ;-)
Note that this is a shell idle time value. It does not monitor an entire session so a user that starts a copy of vi and goes on vacation will still have vi running days later. If you want to enforce the TMOUT value for everyone and not allow them to change it (including root, which is a good idea), use:
export readonly TMOUT=3600
in /etc/profile (this sets POSIX sh, ksh and similar shells). Make sure you assign a value on the same line. Once you set readonly attribute (ie readonly TMOUT) you can't change the value, even if it is null.
	
Bill Hassell, sysadmin
			
			
				
			
			
			
			
			
			
		
		
		
	
	
	
Note that this is a shell idle time value. It does not monitor an entire session so a user that starts a copy of vi and goes on vacation will still have vi running days later. If you want to enforce the TMOUT value for everyone and not allow them to change it (including root, which is a good idea), use:
export readonly TMOUT=3600
in /etc/profile (this sets POSIX sh, ksh and similar shells). Make sure you assign a value on the same line. Once you set readonly attribute (ie readonly TMOUT) you can't change the value, even if it is null.
Bill Hassell, sysadmin
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
		
	
	
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP