News for hackers. Stuff that matters.
Re:Unix System Call Timeouts by klodolph on Monday March 13, 2017 @02:31AM (#13855671)
I think some of the context for "WNOHANG is a bit of a hack" got lost.

> You can sort of work around it by calling waitpid(...WNOHANG) every tenth of a second or so.

For event loops, you can still use SIGCHLD (which is portable) or signalfd (which integrates better into event loops). This avoids the extra syscall every loop through the event loop.

Re:Unix System Call Timeouts by geofft on Monday March 13, 2017 @09:17AM (#13857514)
SIGCHLD (via a signal handler, signalfd, sigtimedwait, whatever) only tells you that some child exited, and also only one part of the process can deal with SIGCHLD. (You can't correctly compose a signal handler + signalfd.) waitpid on the specific pid will check that specific process and no others, and not interfere with any other part of the program that might be waiting for some other child.