2018-07-03 00:15:39 +03:00
<?xml version='1.0'?>
2019-03-14 16:40:58 +03:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2020-11-09 07:23:58 +03:00
<!-- SPDX - License - Identifier: LGPL - 2.1 - or - later -->
2014-09-26 01:27:27 +04:00
2015-11-20 01:38:54 +03:00
<refentry id= "sd_event_add_signal" xmlns:xi= "http://www.w3.org/2001/XInclude" >
2014-09-26 01:27:27 +04:00
<refentryinfo >
<title > sd_event_add_signal</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > sd_event_add_signal</refentrytitle>
<manvolnum > 3</manvolnum>
</refmeta>
<refnamediv >
<refname > sd_event_add_signal</refname>
<refname > sd_event_source_get_signal</refname>
2015-11-20 01:38:54 +03:00
<refname > sd_event_signal_handler_t</refname>
2014-09-26 01:27:27 +04:00
2015-11-20 01:38:54 +03:00
<refpurpose > Add a UNIX process signal event source to an event
loop</refpurpose>
2014-09-26 01:27:27 +04:00
</refnamediv>
<refsynopsisdiv >
<funcsynopsis >
2015-11-20 01:38:54 +03:00
<funcsynopsisinfo > #include < systemd/sd-event.h> </funcsynopsisinfo>
<funcsynopsisinfo > <token > typedef</token> struct sd_event_source sd_event_source;</funcsynopsisinfo>
<funcprototype >
<funcdef > typedef int (*<function > sd_event_signal_handler_t</function> )</funcdef>
<paramdef > sd_event_source *<parameter > s</parameter> </paramdef>
<paramdef > const struct signalfd_siginfo *<parameter > si</parameter> </paramdef>
<paramdef > void *<parameter > userdata</parameter> </paramdef>
</funcprototype>
2014-09-26 01:27:27 +04:00
<funcprototype >
<funcdef > int <function > sd_event_add_signal</function> </funcdef>
<paramdef > sd_event *<parameter > event</parameter> </paramdef>
<paramdef > sd_event_source **<parameter > source</parameter> </paramdef>
<paramdef > int <parameter > signal</parameter> </paramdef>
<paramdef > sd_event_signal_handler_t <parameter > handler</parameter> </paramdef>
<paramdef > void *<parameter > userdata</parameter> </paramdef>
</funcprototype>
<funcprototype >
<funcdef > int <function > sd_event_source_get_signal</function> </funcdef>
<paramdef > sd_event_source *<parameter > source</parameter> </paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
2015-11-20 01:38:54 +03:00
<para > <function > sd_event_add_signal()</function> adds a new UNIX
process signal event source to an event loop. The event loop
object is specified in the <parameter > event</parameter> parameter,
and the event source object is returned in the
<parameter > source</parameter> parameter. The
<parameter > signal</parameter> parameter specifies the numeric
signal to be handled (see <citerefentry
project='man-pages'><refentrytitle > signal</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> ).
The <parameter > handler</parameter> parameter must reference a
function to call when the signal is received or be
<constant > NULL</constant> . The handler function will be passed
the <parameter > userdata</parameter> pointer, which may be chosen
2014-09-26 01:27:27 +04:00
freely by the caller. The handler also receives a pointer to a
2015-11-20 01:38:54 +03:00
<structname > signalfd_siginfo</structname> structure containing
information about the received signal. See <citerefentry
project='man-pages'><refentrytitle > signalfd</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
2014-12-30 19:41:38 +03:00
for further information.</para>
2014-09-26 01:27:27 +04:00
2019-10-30 20:56:03 +03:00
<para > 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 <citerefentry
project='man-pages'><refentrytitle > sigprocmask</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry> or
2015-11-20 01:38:54 +03:00
<citerefentry
sd-event: support callback=NULL in IO/child/inotify/defer event sources, too
Also, document this functionality more prominently, including with a
reference from sd_event_exit().
This is mostly to make things complete, as previously we supported NULL
callbacks only in _add_time() and _add_signal(). However, I think this
makes snese for IO event sources too (think: when some fd such as a pipe
end sees SIGHUP or so, exit), as well as defer or post event sources (i.e. exit
once we got nothing else to do). This also adds support for inotify
event sources, simply to complete things (I can't see the immediate use,
but maybe someone else comes up with it).
The only event source type that doesn't allow callback=NULL now are exit
callbacks, but for them they make little sense, as the event loop is
exiting then anyway.
2020-10-02 10:51:36 +03:00
project='man-pages'><refentrytitle > pthread_sigmask</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ).</para>
2015-11-20 01:38:54 +03:00
<para > By default, the event source is enabled permanently
(<constant > SD_EVENT_ON</constant> ), but this may be changed with
2014-09-26 01:27:27 +04:00
<citerefentry > <refentrytitle > sd_event_source_set_enabled</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> .
If the handler function returns a negative error code, it will be
2015-11-20 01:38:54 +03:00
disabled after the invocation, even if the
<constant > SD_EVENT_ON</constant> mode was requested before.
2014-09-26 01:27:27 +04:00
</para>
2015-11-20 01:38:54 +03:00
<para > To destroy an event source object use
<citerefentry > <refentrytitle > sd_event_source_unref</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
but note that the event source is only removed from the event loop
when all references to the event source are dropped. To make sure
2016-01-05 07:17:21 +03:00
an event source does not fire anymore, even if it is still referenced,
disable the event source using
<citerefentry > <refentrytitle > sd_event_source_set_enabled</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry>
with <constant > SD_EVENT_OFF</constant> .</para>
2015-11-20 01:38:54 +03:00
2015-12-26 20:25:49 +03:00
<para > If the second parameter of
2016-01-05 07:17:21 +03:00
<function > sd_event_add_signal()</function> is
<constant > NULL</constant> no reference to the event source object
is returned. In this case the event source is considered
"floating", and will be destroyed implicitly when the event loop
itself is destroyed.</para>
sd-event: support callback=NULL in IO/child/inotify/defer event sources, too
Also, document this functionality more prominently, including with a
reference from sd_event_exit().
This is mostly to make things complete, as previously we supported NULL
callbacks only in _add_time() and _add_signal(). However, I think this
makes snese for IO event sources too (think: when some fd such as a pipe
end sees SIGHUP or so, exit), as well as defer or post event sources (i.e. exit
once we got nothing else to do). This also adds support for inotify
event sources, simply to complete things (I can't see the immediate use,
but maybe someone else comes up with it).
The only event source type that doesn't allow callback=NULL now are exit
callbacks, but for them they make little sense, as the event loop is
exiting then anyway.
2020-10-02 10:51:36 +03:00
<para > If the <parameter > handler</parameter> parameter to <function > sd_event_add_signal()</function> is
<constant > NULL</constant> , and the event source fires, this will be considered a request to exit the
event loop. In this case, the <parameter > userdata</parameter> parameter, cast to an integer, is passed as
the exit code parameter to
<citerefentry > <refentrytitle > sd_event_exit</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> .</para>
2016-01-05 07:17:21 +03:00
<para > <function > sd_event_source_get_signal()</function> returns
the configured signal number of an event source created previously
with <function > sd_event_add_signal()</function> . It takes the
event source object as the <parameter > source</parameter>
2014-09-26 01:27:27 +04:00
parameter.</para>
</refsect1>
<refsect1 >
<title > Return Value</title>
<para > On success, these functions return 0 or a positive
integer. On failure, they return a negative errno-style error
2016-01-05 07:17:21 +03:00
code.</para>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<refsect2 >
<title > Errors</title>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<para > Returned errors may indicate the following problems:</para>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<variablelist >
<varlistentry >
<term > <constant > -ENOMEM</constant> </term>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<listitem > <para > Not enough memory to allocate an object.</para> </listitem>
</varlistentry>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<varlistentry >
<term > <constant > -EINVAL</constant> </term>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<listitem > <para > An invalid argument has been passed.</para> </listitem>
</varlistentry>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<varlistentry >
<term > <constant > -EBUSY</constant> </term>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<listitem > <para > A handler is already installed for this
signal or the signal was not blocked previously.</para> </listitem>
</varlistentry>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<varlistentry >
<term > <constant > -ESTALE</constant> </term>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<listitem > <para > The event loop is already terminated.</para> </listitem>
</varlistentry>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<varlistentry >
<term > <constant > -ECHILD</constant> </term>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<listitem > <para > The event loop has been created in a different process.</para> </listitem>
</varlistentry>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<varlistentry >
<term > <constant > -EDOM</constant> </term>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
<listitem > <para > The passed event source is not a signal event source.</para> </listitem>
</varlistentry>
2014-09-26 01:27:27 +04:00
2019-03-21 16:53:00 +03:00
</variablelist>
</refsect2>
2014-09-26 01:27:27 +04:00
</refsect1>
2015-11-20 01:38:54 +03:00
<xi:include href= "libsystemd-pkgconfig.xml" />
2014-09-26 01:27:27 +04:00
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > sd-event</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > sd_event_new</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
2015-11-20 01:38:54 +03:00
<citerefentry > <refentrytitle > sd_event_now</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > sd_event_add_io</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
2014-09-26 01:27:27 +04:00
<citerefentry > <refentrytitle > sd_event_add_time</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
2014-09-26 01:27:33 +04:00
<citerefentry > <refentrytitle > sd_event_add_child</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
2018-05-29 16:59:26 +03:00
<citerefentry > <refentrytitle > sd_event_add_inotify</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
2014-09-26 01:27:40 +04:00
<citerefentry > <refentrytitle > sd_event_add_defer</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
2015-11-20 01:38:54 +03:00
<citerefentry > <refentrytitle > sd_event_source_set_enabled</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > sd_event_source_set_description</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > sd_event_source_set_userdata</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
2019-11-27 19:11:44 +03:00
<citerefentry > <refentrytitle > sd_event_source_set_floating</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
2015-11-20 01:38:54 +03:00
<citerefentry project= 'man-pages' > <refentrytitle > signal</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> ,
2019-10-30 20:56:03 +03:00
<citerefentry project= 'man-pages' > <refentrytitle > signalfd</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry> ,
<citerefentry project= 'man-pages' > <refentrytitle > sigprocmask</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry> ,
<citerefentry project= 'man-pages' > <refentrytitle > pthread_sigmask</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry>
2014-09-26 01:27:27 +04:00
</para>
</refsect1>
</refentry>