You are not logged in.
Pages: 1
Hi all,
My program currently uses a signal handler to catch CTRL-C events. The signal handler simply sets a boolean variable. The program's main event loop then polls the boolean every second or so, and if it sees that it has been set, it cleans up and exits.
This works, more or less, but it means that my program can never be completely idle, it must always wake up and poll every second, which seems like a wasteful/ugly way to do things.
On another discussion site I saw someone recommend setting up a socket pair, and having the signal handler close one of the sockets. The main loop would then select() (or poll()) on that socket, and thus be notified when the signal handler had closed the other one.
My question is, will that work reliably? I had been under the impression that signal handlers weren't allowed to execute socket routines; but perhaps simply closing a socket (or alternatively, send()-ing a byte on it) would be safe enough?
Bonus question: Windows has a function somewhat similar to signals in its SetConsoleCtrlHandler() function. Would a similar scheme work there?
Offline
Thanks for the help guys; I've rewritten my signal handler to send a byte on a socket instead of setting a boolean, and it appears to be working well.
-Jeremy
Offline
Fascinating... I never knew it was impossible for select() (and company) to ever be
auto-restarted... It makes perfect sense, now that I think about it, though...
Where'd you pull that quote from, i3839? I'm just curious to see the rest of the list of
non-restartable functions... I don't see it in my local sigaction man page, which was
the first place I looked for it...
Offline
Offline
Pages: 1