14 Jul
2003
14 Jul
'03
18:38
On Mon, 2003-07-14 at 20:34, Clayton Cornell wrote:
So.. here's the question... how can I release the 4662 port that has been "claimed" by the crashed application? I cannot find anything in my process list that is hanging around after the crash. I don't know what else to look for to find what is keeping port 4662 engaged. Rebooting seems like a silly way to correct a problem. So... any ideas or suggestions?
try "fuser 4662/tcp" and see which process is holding the port. And you're right, a reboot shouldn't be necessary. As soon as the app holding the port exits (for whatever reason) the port should be released. So I have to assume it hasn't exited