| |||||||||||||
Ghosts of Unix past, part 3: Unfixable designsGhosts of Unix past, part 3: Unfixable designsPosted Nov 16, 2010 17:33 UTC (Tue) by michaeljt (subscriber, #39183)In reply to: Ghosts of Unix past, part 3: Unfixable designs by foom Parent article: Ghosts of Unix past, part 3: Unfixable designs
> Signalfd isn't intended for "specialized" applications of signals (and I'm not sure how named pipes come into play at all). It would be nice to use for completely normal uses of signal handling: for example, it would be ideal for replacing a SIGCHLD handler in an application with an event loop [...]
That makes sense - and obviously a named pipe would be no good there whatsoever. I was more thinking of things like SIGUSR1 sorts of interactions.
(Log in to post comments)
|
|||||||||||||