Re: [perl #93428] potential race condition when mixing signals andselect()

On Sun, Dec 11, 2011 at 11:55:40AM -0800, Leon Timmermans via RT wrote:
> > it seems there is a race condition when mixing signals and select().
> > 
> > A solution is to use pselect() instead of select() when available.
> 
> This is *not* a perl bug. but a fundamental difficulty in dealing with
> signals. I suggest closing this ticket.

I agree. It's a well-known limitation in the API design of select(2).

pselect(2) and ppoll(2) work around it. E.g. note my own IO::Ppoll, an
IO::Poll-compatible dropin replacement that uses ppoll(2).

-- 
Paul "LeoNerd" Evans

leonerd@leonerd.org.uk
ICQ# 4135350       |  Registered Linux# 179460
http://www.leonerd.org.uk/

• [perl #93428] potential race condition when mixing signals and select() by Leon Timmermans via RT
• Re: [perl #93428] potential race condition when mixing signals andselect() by Paul LeoNerd Evans
• Re: [perl #93428] potential race condition when mixing signals and select() by Eric Brine
• Re: [perl #93428] potential race condition when mixing signals and select() by Leon Timmermans
• Re: [perl #93428] potential race condition when mixing signals and select() by Leon Timmermans
• Re: [perl #93428] potential race condition when mixing signals and select() by Eric Brine
• Re: [perl #93428] potential race condition when mixing signals and select() by Eric Brine
• [perl #93428] potential race condition when mixing signals and select() by Father Chrysostomos via RT