From: Lennart Poettering Date: Wed, 30 Oct 2019 17:56:03 +0000 (+0100) Subject: man: don't claim we'd unblock the specified signal in sd_event_add_signal() X-Git-Tag: v245-rc1~315^2~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=68765d94fec8a053f6036d67fd9ce84497410755;p=thirdparty%2Fsystemd.git man: don't claim we'd unblock the specified signal in sd_event_add_signal() We don't, the signal remains blocked. We use signalfd() to be able to read the signal events without unblocking the signal. While we are at it, mention that pthread_sigmask() is fine too. --- diff --git a/man/sd_event_add_signal.xml b/man/sd_event_add_signal.xml index a7148ca8dd1..43794bd7ceb 100644 --- a/man/sd_event_add_signal.xml +++ b/man/sd_event_add_signal.xml @@ -75,14 +75,13 @@ project='man-pages'>signalfd2 for further information. - Only a single handler may be installed for a specific - signal. The signal will be unblocked by this call, and must be - blocked before this function is called in all threads (using + Only a single handler may be installed for a specific signal. The signal must be blocked in all + threads before this function is called (using sigprocmask2 or sigprocmask2). If - the handler is not specified (handler is - NULL), a default handler which causes the - program to exit cleanly will be used. + project='man-pages'>pthread_sigmask3). If + the handler is not specified (handler is NULL), a default + handler which causes the program to exit cleanly will be used. By default, the event source is enabled permanently (SD_EVENT_ON), but this may be changed with @@ -189,7 +188,9 @@ sd_event_source_set_userdata3, sd_event_source_set_floating3, signal7, - signalfd2 + signalfd2, + sigprocmask2, + pthread_sigmask3