|
in reply to forcibly closing sockets/unbinding ports - win32
Win32 or otherwise, I don't think there's a way to force a process to relinquish a port it's listening on, short of terminating the process.
However, you might be able to work around it. You could write a small app that binds to port 110 itself, then spawns/executes/otherwise launches program X, then relinquishes port 110.
This depends on program X successfully going on it's merry way if it fails to bind to port 110, which may or may not be the case.
Good luck.
Peace,
-McD
|
