I'm writing a very simple server that loops forever until Ctrl-C is pressed. I'd like to have the signal handler for ctrl-c close the open sockets and shut down the server, but I don't know what the scope is for a signal handler, and I don't like the idea of declaring the socket(s) I would need to close to be global.
Can someone offer suggestions? Is there some standard way to do this?
Signal handlers can be specified for all but two signals (SIGKILL and SIGSTOP cannot be caught, blocked or ignored). If the signal reports an error within the program (and the signal is not asynchronous), the signal handler can terminate by calling abort() , exit() , or longjmp() .
The C standard pretty much only allows you to do one thing in a signal handler that affects global state. Set a volatile sig_atomic_t variable. Calling printf , sleep and such in a signal handler is not allowed.
The signal handler can indeed be interrupted by another signal (assuming it isn't the same signal as the one which invoked the handler in the first place). your handler can still be interrupted by delivery of another kind of signal.
24.4. 1 Signal Handlers that ReturnSee Program Error Signals. Handlers that return normally must modify some global variable in order to have any effect. Typically, the variable is one that is examined periodically by the program during normal operation.
Well, since you have signal handlers, I'm going to assume you're on a Unix variant. If so:
socket(2)
.So, it's perfectly valid in your signal handler. How you make your signal handler aware of which number to use depends on the language you're writing in, which you didn't specify. There are two approaches that will work in pretty much any language
close
and exit, just call exit. Or set the signal action to default, which is exit. The kernel will close the sockets.If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With