Re: pselect and signal handling issue

[Thor Lancelot Simon <tls%panix.com@localhost>]

On Wed, May 18, 2011 at 03:52:24AM +0000, Christos Zoulas wrote:
> In article <20110517155445.GA13094%panix.com@localhost>,
> Thor Lancelot Simon  <tls%panix.com@localhost> wrote:
> >On Tue, May 17, 2011 at 05:10:42PM +0200, anthony viallard wrote:
> >> Hi,
> >> 
> >> I have an issue with netBSD 5.1. My problem is related to
> >> 
> >>  * http://mail-index.netbsd.org/netbsd-users/2010/07/10/msg006559.html
> >>  * http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=43625
> >> 
> >> but seem the issue isn't fixed.
> >> 
> >> I'm the developper of yaddns (https://github.com/yaddns/yaddns), a
> >> small program to use dyndns services (no-ip, dyndns.org, ...). I'm
> >> trying to porting yaddns (developped on Linux) on NetBSD but i have
> >> found a problem with pselect and signals handling.
> >> 
> >> In my program, i install signal handler for SIGHUP, SIGTERM, SIGINT,
> >> SIGUSR1 and SIGUSR2 signals. In this signal handler, i modify global
> >> variables to inform what signal was received. As i want to process
> >> signals only in "waiting state", i use pselect() with a sigset empty.
> >> If pselect() return -1 and errno = EINTR, i known signal was caught.
> >
> >Ewwww!
> >
> >Have you considered using libevent?
> 
> This is not the answer he expected. Our pselect(2) was broken and has
> been fixed on head.

Well, it may not be the answer he expected, but I think it might do him
a lot more good in the long run.

Any use of pselect() is pretty awful.  This one doubly so.

Thor