- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Question about port hang
Operating System - HP-UX
1755662
Members
3440
Online
108837
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
тАО10-06-2004 06:58 AM
тАО10-06-2004 06:58 AM
My DBA has a program written in Perl that allows a machine to connect to port 9991. This program sits in a listen state until it gets a request. At the time someone telnets to this port a connection is established with a new forked process. When closing this connection the forked process is closed, you can't see it anymore with a ps -ef. But if you do a netstat -an |grep 9991 you can still see the connection in close_wait. The odd thing about this is if you were to do multiple telnets to 9991 and close each one they all close properly except for the first process that is closed. This one stays in a close_wait state. Any idea what could cause this???
Thanks,
Jason
Thanks,
Jason
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2004 07:15 AM
тАО10-06-2004 07:15 AM
Solution
Jason,
There is a ton of useless....um, I mean, useful information in this thread. Perhaps it will help you.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=671167
Dwyane :)
There is a ton of useless....um, I mean, useful information in this thread. Perhaps it will help you.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=671167
Dwyane :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2004 07:35 AM
тАО10-06-2004 07:35 AM
Re: Question about port hang
Tell your DBA to use shutdown() rather than close() on his sockets. I'll quote the perlfunc manpage under shutdown:
Quote -----------
shutdown(SOCKET,0); # stopped reading data
shutdown(SOCKET,1); # stopped writing data
shutdown(SOCKET,2); # stopping using this socket
This is useful with sockets when you want to tell the other side you're done writing but not done reading, or vice versa. It's also a more insistant form of close because it also disables the file descriptors in any forked copies in other processes.
------------- Endquote
The good news is that shudown() is also available as an IO::Socket method as well so
that $mysocket->shutdown(2); will work as well.
Quote -----------
shutdown(SOCKET,0); # stopped reading data
shutdown(SOCKET,1); # stopped writing data
shutdown(SOCKET,2); # stopping using this socket
This is useful with sockets when you want to tell the other side you're done writing but not done reading, or vice versa. It's also a more insistant form of close because it also disables the file descriptors in any forked copies in other processes.
------------- Endquote
The good news is that shudown() is also available as an IO::Socket method as well so
that $mysocket->shutdown(2); will work as well.
If it ain't broke, I can fix that.
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