- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: netstat TIME_WAIT
Operating System - HP-UX
1755266
Members
4975
Online
108831
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
Discussions
Discussions
Forums
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
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
тАО06-29-2005 07:44 AM
тАО06-29-2005 07:44 AM
Dear Sirs,
I am working on HP Apache web server on hpux 11. I gave "netstat -an" command. I saw the output as "TIME_WAIT". I am not able to figure out whether it is good or bad ?
Any help appreciated.
Thanks,
Shiv
I am working on HP Apache web server on hpux 11. I gave "netstat -an" command. I saw the output as "TIME_WAIT". I am not able to figure out whether it is good or bad ?
Any help appreciated.
Thanks,
Shiv
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2005 08:25 AM
тАО06-29-2005 08:25 AM
Re: netstat TIME_WAIT
The TIME_WAIT state occurs after the socket is closed out. The system is monitoring the socket descriptor and will not release it for a few minutes. It's waiting for any delayed packets to turn up from the remote host after acknowledging the connection termination request.
The TIME_WAIT state prevents old socket connections from being reused before all data is 'flushed' off the network.
You can view it with:
# ndd -get /dev/tcp tcp_time_wait_interval
and set it with:
# ndd -set /dev/tcp tcp_time_wait_interval xxxxx
cheers!
The TIME_WAIT state prevents old socket connections from being reused before all data is 'flushed' off the network.
You can view it with:
# ndd -get /dev/tcp tcp_time_wait_interval
and set it with:
# ndd -set /dev/tcp tcp_time_wait_interval xxxxx
cheers!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2005 06:30 PM
тАО06-29-2005 06:30 PM
Re: netstat TIME_WAIT
See tha attachment
It is normal to have a socket in the TIME_WAIT state for a long period of time. The time is specified in RFC793 as twice the Maximum Segment Lifetime (MSL). MSL is specified to be 2 minutes. So, a socket could be in a TIME_WAIT state for as long as 4 minutes. Some systems implement different values (less than 2 minutes) for the MSL.
It is normal to have a socket in the TIME_WAIT state for a long period of time. The time is specified in RFC793 as twice the Maximum Segment Lifetime (MSL). MSL is specified to be 2 minutes. So, a socket could be in a TIME_WAIT state for as long as 4 minutes. Some systems implement different values (less than 2 minutes) for the MSL.
Be Always Joy ......
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-30-2005 05:51 AM
тАО06-30-2005 05:51 AM
Solution
Strictly speaking, TIME_WAIT is about TCP connections, which are named by the four-tuple of local/remote IP and local/remote port number. By the time a TCP connection has entered TIME_WAIT, the socket is (virtually always) long gone.
It is highly unlikely that anyone would ever need to shorten tcp_time_wait_interval.
The HP-UX TCP stack can deal with a great many connections in TIME_WAIT.
Any application that cannot restart while there are connections in TIME_WAIT is broken.
It is highly unlikely that anyone would ever need to shorten tcp_time_wait_interval.
The HP-UX TCP stack can deal with a great many connections in TIME_WAIT.
Any application that cannot restart while there are connections in TIME_WAIT is broken.
there is no rest for the wicked yet the virtuous have no pillows
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP