Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Recover from a runaway netstat process' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Recover from a runaway netstat process
Authored by: MattHaffner on Aug 23, '04 03:06:00PM

There was also a GeekTool hint that had a nice netstat output in it to show open ports. Be careful with these though--they can be resource hungry. By default netstat tries to reverse map all the IP numbers in its output. You can stop this by adding '-n' to the command line.

It's possible that netstat could be hanging or at least stalling if the DNS server isn't available (like wireless goes out of range, wake from sleep before network is fully up, etc.). If you have a frequently running netstat that's trying to resolve names, you could be taking a noticeable hit on performance. Although it's nice to know what's going on all the time, I put an open port monitor in a GeekTool subset and only turn it on if I am currently interested in that info.



[ Reply to This | # ]