[New-bugs-announce] [issue12304] expose signalfd(2) in the signal module

STINNER Victor report at bugs.python.org
Fri Jun 10 01:00:56 CEST 2011


New submission from STINNER Victor <victor.stinner at haypocalc.com>:

"Linux offers the signalfd syscall since 2.6.22 (with minor changes afterwards).  This call allows signals to be handled as bytes read out of a file descriptor, rather than as interruptions to the flow of a program.  Quite usefully, this file descriptor can be select()'d on (or poll()'d, epoll()'d, etc) alongside other "normal" file descriptors.

In order to effectively use signalfd(), the signals in question must be blocked, though.  So it makes sense to expose sigprocmask(2) at the same time, in order to allow this blocking to be set up."

This message is copy/pasted from #8407 (msg103182). I created the issue because #8407 contains much more than signalfd().

----------
components: Extension Modules
messages: 138034
nosy: exarkun, haypo
priority: normal
severity: normal
status: open
title: expose signalfd(2) in the signal module
versions: Python 3.3

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12304>
_______________________________________


More information about the New-bugs-announce mailing list