Linux port closing problem

[raczzoli]

Hello.

I recently wrote an application which listens on a specified port, but if I stop the application and start it again it cannot bind the socket to the same port. I have to wait some time, after the operating system frees the port. As I know this problem isn`t specific to linux.

Can somebody tell me if there is any solution to this issue?

Thank you.

[Fordy]

Did you close the socket before exiting?

[raczzoli]

To be honest no. The problem is that if I run the application the only way I can stop it is by pressing ctrl+c, and not really sure how to call the close() command before.

[Fordy]

Post your code

[raczzoli]

The problem is that the source code is pretty big, and I can`t post it here. Without the source code can`t you help me?

My question is how should I execute close() before I press ctrl+c. It would be a possibility to intercept the keypress, close the socket, and than stop the application?

[_Mike]

To be honest no. The problem is that if I run the application the only way I can stop it is by pressing ctrl+c, and not really sure how to call the close() command before.

Trap the signal ctrl-c sends?

[valthyx]

setsockopt(), getsockopt()
This could solve. See the "SO_REUSEADDR" option.

[CommonTater]

To be honest no. The problem is that if I run the application the only way I can stop it is by pressing ctrl+c, and not really sure how to call the close() command before.

Do you have access to the source code?
If so fix the problem...
Write an orderly shutdown routine that closes the port on the way out.

[raczzoli]

Hi.

Thank you all for the suggestions.

I tried the setsockopt() with SO_REUSEADDR and it works.

Thank you again

[Codeplug]

>> I tried the setsockopt() with SO_REUSEADDR and it works.
All you've managed to do is hide one symptom of a root problem. Fix the root problem.

How do you know your process has even exited? Have you looked at the running processes with something like ps?

gg