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:11:38PM

One other tip to help find out who spawned off the netstat originally:

Open the Activity Monitor and double-click on the netstat process that's sucking up CPU. In the window that pops up, the 'Parent Process' field should be helpful to trace where the command started from. You can even click on the parent process and follow the chain of commands further back.

From the terminal, 'ps' can give you this information as well with the 'l' listing option. The PPID field has the parent process ID. Of course you have to do the tracing back by hand in that case, but it's very scriptable then.



[ Reply to This | # ]
netstat is from the set-hostname script
Authored by: hayne on Aug 23, '04 07:36:25PM

One of the people who have been struggling with this issue in the forums had discovered that the errant 'netstat' process was started from a script named 'set-hostname' which was started via 'configd'. See the forum thread for more details. I have just added a summary there:
http://forums.macosxhints.com/showthread.php?t=23485



[ Reply to This | # ]