On Wed, Jun 12, 2013 at 10:56:25PM +0200, Lionel Cons wrote:
>
> The use of sighold() may be the culprit for some issues. The Linux
> manpage clearly says " This API is obsolete: new appli-
> cations should use the POSIX signal API (sigaction(2),
> sigprocmask(2), etc.)". On some platforms its even not possible to
> safely mix sighold() with sigaction() without loosing signals.
>
> The other issue which jumped in my eye is that the queue management is
> far from async signal safe and that the natural ordering of signals is
> badly disturbed by processing them by signal number instead of the
> order they've been received.
>
> Did anyone thought about the idea of using signalfd() instead?
AFAIK signalfd() is very specific to Linux ...
Werner
--
"Having a smoking section in a restaurant is like having
a peeing section in a swimming pool." -- Edward Burr
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
