- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Telnet problem, please help me.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО09-22-2006 03:57 PM
тАО09-22-2006 03:57 PM
The parameters in /etc/rc.config.d/nddconf are not configed.
ndd -h tcp_ip_abort_interval
return 10 minutes
tcp_ip_abort_cinterval
return 75 seconds
Then I try to set the TMOUT=14400 in .profile, it doesn't work.
Is there any other paramters about the telnet timeout?
And what can I do ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-22-2006 04:06 PM
тАО09-22-2006 04:06 PM
Re: Telnet problem, please help me.
env | grep TMOUT
if this returns nothing or
TMOUT=0
it means that it is disabled.
If it is disabled, only place to look is the network equipment default timeouts.
hope this helps
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-22-2006 08:06 PM
тАО09-22-2006 08:06 PM
Re: Telnet problem, please help me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-23-2006 03:14 AM
тАО09-23-2006 03:14 AM
Re: Telnet problem, please help me.
export TMOUT=1800
readonly TMOUT
Note that if you put the change in .profile, users can change .profile at any time. Note also that if a user just runs another process (like vi), the timer stops.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-23-2006 01:15 PM
тАО09-23-2006 01:15 PM
Re: Telnet problem, please help me.
You are right, but this can't resolve my problem. I want to make the telnet not be terminated. The parameter TMOUT doesn't work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-23-2006 02:42 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-24-2006 10:00 PM
тАО09-24-2006 10:00 PM
Re: Telnet problem, please help me.
When a session terminated by TIMEOUT, user will receive a message like this:
shell time out in 60 seconds
ksh: timed out waiting for input
logout
Connection closed.
If user received something else, can you post it here? may be we can understand a pit more from the message.
Yang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 05:56 AM
тАО09-25-2006 05:56 AM
Re: Telnet problem, please help me.
Bill Hassell, sysadmin