2018-07-02 21:15:39 +00:00
|
|
|
<?xml version='1.0'?>
|
2019-03-14 13:40:58 +00: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 04:23:58 +00:00
|
|
|
<!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2015-11-19 22:38:54 +00:00
|
|
|
<refentry id="sd_event_add_time" xmlns:xi="http://www.w3.org/2001/XInclude">
|
2014-05-06 16:51:08 +00:00
|
|
|
|
|
|
|
<refentryinfo>
|
|
|
|
<title>sd_event_add_time</title>
|
|
|
|
<productname>systemd</productname>
|
|
|
|
</refentryinfo>
|
|
|
|
|
|
|
|
<refmeta>
|
|
|
|
<refentrytitle>sd_event_add_time</refentrytitle>
|
|
|
|
<manvolnum>3</manvolnum>
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
<refnamediv>
|
|
|
|
<refname>sd_event_add_time</refname>
|
2020-11-10 13:20:06 +00:00
|
|
|
<refname>sd_event_add_time_relative</refname>
|
2014-05-06 16:51:08 +00:00
|
|
|
<refname>sd_event_source_get_time</refname>
|
|
|
|
<refname>sd_event_source_set_time</refname>
|
2020-11-10 13:20:06 +00:00
|
|
|
<refname>sd_event_source_set_time_relative</refname>
|
2014-05-06 16:51:08 +00:00
|
|
|
<refname>sd_event_source_get_time_accuracy</refname>
|
|
|
|
<refname>sd_event_source_set_time_accuracy</refname>
|
|
|
|
<refname>sd_event_source_get_time_clock</refname>
|
2015-11-19 22:38:54 +00:00
|
|
|
<refname>sd_event_time_handler_t</refname>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
|
|
|
<refpurpose>Add a timer event source to an event loop</refpurpose>
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
|
|
|
<funcsynopsis>
|
2015-11-19 22:38:54 +00: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_time_handler_t</function>)</funcdef>
|
|
|
|
<paramdef>sd_event_source *<parameter>s</parameter></paramdef>
|
|
|
|
<paramdef>uint64_t <parameter>usec</parameter></paramdef>
|
|
|
|
<paramdef>void *<parameter>userdata</parameter></paramdef>
|
|
|
|
</funcprototype>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
|
|
|
<funcprototype>
|
|
|
|
<funcdef>int <function>sd_event_add_time</function></funcdef>
|
|
|
|
<paramdef>sd_event *<parameter>event</parameter></paramdef>
|
|
|
|
<paramdef>sd_event_source **<parameter>source</parameter></paramdef>
|
|
|
|
<paramdef>clockid_t <parameter>clock</parameter></paramdef>
|
|
|
|
<paramdef>uint64_t <parameter>usec</parameter></paramdef>
|
|
|
|
<paramdef>uint64_t <parameter>accuracy</parameter></paramdef>
|
|
|
|
<paramdef>sd_event_time_handler_t <parameter>handler</parameter></paramdef>
|
2014-05-07 23:28:46 +00:00
|
|
|
<paramdef>void *<parameter>userdata</parameter></paramdef>
|
2014-05-06 16:51:08 +00:00
|
|
|
</funcprototype>
|
|
|
|
|
2020-07-28 09:18:08 +00:00
|
|
|
<funcprototype>
|
|
|
|
<funcdef>int <function>sd_event_add_time_relative</function></funcdef>
|
|
|
|
<paramdef>sd_event *<parameter>event</parameter></paramdef>
|
|
|
|
<paramdef>sd_event_source **<parameter>source</parameter></paramdef>
|
|
|
|
<paramdef>clockid_t <parameter>clock</parameter></paramdef>
|
|
|
|
<paramdef>uint64_t <parameter>usec</parameter></paramdef>
|
|
|
|
<paramdef>uint64_t <parameter>accuracy</parameter></paramdef>
|
|
|
|
<paramdef>sd_event_time_handler_t <parameter>handler</parameter></paramdef>
|
|
|
|
<paramdef>void *<parameter>userdata</parameter></paramdef>
|
|
|
|
</funcprototype>
|
|
|
|
|
2014-05-06 16:51:08 +00:00
|
|
|
<funcprototype>
|
|
|
|
<funcdef>int <function>sd_event_source_get_time</function></funcdef>
|
|
|
|
<paramdef>sd_event_source *<parameter>source</parameter></paramdef>
|
2015-11-19 22:38:54 +00:00
|
|
|
<paramdef>uint64_t *<parameter>usec</parameter></paramdef>
|
2014-05-06 16:51:08 +00:00
|
|
|
</funcprototype>
|
|
|
|
|
|
|
|
<funcprototype>
|
|
|
|
<funcdef>int <function>sd_event_source_set_time</function></funcdef>
|
|
|
|
<paramdef>sd_event_source *<parameter>source</parameter></paramdef>
|
2015-11-19 22:38:54 +00:00
|
|
|
<paramdef>uint64_t <parameter>usec</parameter></paramdef>
|
2014-05-06 16:51:08 +00:00
|
|
|
</funcprototype>
|
|
|
|
|
2020-07-28 09:18:08 +00:00
|
|
|
<funcprototype>
|
|
|
|
<funcdef>int <function>sd_event_source_set_time_relative</function></funcdef>
|
|
|
|
<paramdef>sd_event_source *<parameter>source</parameter></paramdef>
|
|
|
|
<paramdef>uint64_t <parameter>usec</parameter></paramdef>
|
|
|
|
</funcprototype>
|
|
|
|
|
2014-05-06 16:51:08 +00:00
|
|
|
<funcprototype>
|
|
|
|
<funcdef>int <function>sd_event_source_get_time_accuracy</function></funcdef>
|
|
|
|
<paramdef>sd_event_source *<parameter>source</parameter></paramdef>
|
2015-11-19 22:38:54 +00:00
|
|
|
<paramdef>uint64_t *<parameter>usec</parameter></paramdef>
|
2014-05-06 16:51:08 +00:00
|
|
|
</funcprototype>
|
|
|
|
|
|
|
|
<funcprototype>
|
|
|
|
<funcdef>int <function>sd_event_source_set_time_accuracy</function></funcdef>
|
|
|
|
<paramdef>sd_event_source *<parameter>source</parameter></paramdef>
|
2015-11-19 22:38:54 +00:00
|
|
|
<paramdef>uint64_t <parameter>usec</parameter></paramdef>
|
2014-05-06 16:51:08 +00:00
|
|
|
</funcprototype>
|
|
|
|
|
|
|
|
<funcprototype>
|
|
|
|
<funcdef>int <function>sd_event_source_get_time_clock</function></funcdef>
|
|
|
|
<paramdef>sd_event_source *<parameter>source</parameter></paramdef>
|
|
|
|
<paramdef>clockid_t *<parameter>clock</parameter></paramdef>
|
|
|
|
</funcprototype>
|
|
|
|
|
|
|
|
</funcsynopsis>
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Description</title>
|
|
|
|
|
2016-01-31 23:20:18 +00:00
|
|
|
<para><function>sd_event_add_time()</function> adds a new timer event source to an event loop. The event loop
|
|
|
|
object is specified in the <parameter>event</parameter> parameter, the event source object is returned in the
|
|
|
|
<parameter>source</parameter> parameter. The <parameter>clock</parameter> parameter takes a clock identifier, one
|
|
|
|
of <constant>CLOCK_REALTIME</constant>, <constant>CLOCK_MONOTONIC</constant>, <constant>CLOCK_BOOTTIME</constant>,
|
|
|
|
<constant>CLOCK_REALTIME_ALARM</constant>, or <constant>CLOCK_BOOTTIME_ALARM</constant>. See
|
|
|
|
<citerefentry><refentrytitle>timerfd_create</refentrytitle><manvolnum>2</manvolnum></citerefentry> for details
|
|
|
|
regarding the various types of clocks. The <parameter>usec</parameter> parameter specifies the earliest time, in
|
|
|
|
microseconds (µs), relative to the clock's epoch, when the timer shall be triggered. If a time already in the past
|
|
|
|
is specified (including <constant>0</constant>), this timer source "fires" immediately and is ready to be
|
2016-07-12 10:52:11 +00:00
|
|
|
dispatched. If the parameter is specified as <constant>UINT64_MAX</constant> the timer event will never elapse,
|
2016-01-31 23:20:18 +00:00
|
|
|
which may be used as an alternative to explicitly disabling a timer event source with
|
|
|
|
<citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>. The
|
|
|
|
<parameter>accuracy</parameter> parameter specifies an additional accuracy value in µs specifying how much the
|
|
|
|
timer event may be delayed. Use <constant>0</constant> to select the default accuracy (250ms). Use 1µs for maximum
|
|
|
|
accuracy. Consider specifying 60000000µs (1min) or larger for long-running events that may be delayed
|
|
|
|
substantially. Picking higher accuracy values allows the system to coalesce timer events more aggressively,
|
2022-01-05 13:00:59 +00:00
|
|
|
improving power efficiency.</para>
|
|
|
|
|
|
|
|
<para>The <parameter>handler</parameter> is a function to call when the timer elapses or
|
|
|
|
<constant>NULL</constant>. The <parameter>userdata</parameter> pointer will be passed to the handler
|
|
|
|
function, and may be chosen freely by the caller. The configured trigger time is also passed to the
|
|
|
|
handler, even if the call actually happens slightly later, subject to the specified accuracy value, the
|
|
|
|
kernel timer slack (see
|
|
|
|
<citerefentry><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>), and
|
|
|
|
additional scheduling latencies. To query the actual time the handler was called use
|
|
|
|
<citerefentry><refentrytitle>sd_event_now</refentrytitle><manvolnum>3</manvolnum></citerefentry>. The
|
|
|
|
handler may return negative to signal an error (see below), other return values are ignored. If
|
|
|
|
<parameter>handler</parameter> is <constant>NULL</constant>, a default handler that calls
|
|
|
|
<citerefentry><refentrytitle>sd_event_exit</refentrytitle><manvolnum>3</manvolnum></citerefentry> will be
|
|
|
|
used.</para>
|
|
|
|
|
|
|
|
<para>By default, the timer will elapse once (<constant>SD_EVENT_ONESHOT</constant>), but this may be
|
|
|
|
changed with
|
2014-09-25 21:27:27 +00:00
|
|
|
<citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
|
2022-01-05 13:00:59 +00:00
|
|
|
If the handler function returns a negative error code, it will either be disabled after the invocation,
|
|
|
|
even if the <constant>SD_EVENT_ON</constant> mode was requested before, or it will cause the loop to
|
|
|
|
terminate, see
|
|
|
|
<citerefentry><refentrytitle>sd_event_source_set_exit_on_failure</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
|
|
|
|
Note that a timer event set to <constant>SD_EVENT_ON</constant> will fire continuously unless its
|
|
|
|
configured time is updated using <function>sd_event_source_set_time()</function>.</para>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2020-07-28 09:18:08 +00:00
|
|
|
<para><function>sd_event_add_time_relative()</function> is like <function>sd_event_add_time()</function>,
|
|
|
|
but takes a relative time specification. It's relative to the current time of the event loop iteration,
|
|
|
|
as returned by
|
|
|
|
<citerefentry><refentrytitle>sd_event_now</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
|
|
|
|
|
2015-11-19 22:38:54 +00: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 04:17:21 +00: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-19 22:38:54 +00:00
|
|
|
|
2015-12-26 17:25:49 +00:00
|
|
|
<para>If the second parameter of
|
2016-01-05 04:17:21 +00:00
|
|
|
<function>sd_event_add_time()</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>
|
2015-11-19 22:38:54 +00:00
|
|
|
|
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 07:51:36 +00:00
|
|
|
<para>If the <parameter>handler</parameter> parameter to <function>sd_event_add_time()</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
|
2015-11-19 22:38:54 +00:00
|
|
|
<citerefentry><refentrytitle>sd_event_exit</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
|
|
|
|
|
|
|
|
<para>Use <constant>CLOCK_BOOTTIME_ALARM</constant> and
|
|
|
|
<constant>CLOCK_REALTIME_ALARM</constant> to define event sources
|
|
|
|
that may wake up the system from suspend.</para>
|
|
|
|
|
|
|
|
<para>In order to set up relative timers (that is, relative to the
|
|
|
|
current time), retrieve the current time via
|
|
|
|
<citerefentry><refentrytitle>sd_event_now</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
2016-01-05 04:17:21 +00:00
|
|
|
add the desired timespan to it, and use the result as
|
2015-11-19 22:38:54 +00:00
|
|
|
the <parameter>usec</parameter> parameter to
|
|
|
|
<function>sd_event_add_time()</function>.</para>
|
|
|
|
|
|
|
|
<para>In order to set up repetitive timers (that is, timers that
|
|
|
|
are triggered in regular intervals), set up the timer normally,
|
|
|
|
for the first invocation. Each time the event handler is invoked,
|
|
|
|
update the timer's trigger time with
|
|
|
|
<citerefentry><refentrytitle>sd_event_source_set_time</refentrytitle><manvolnum>3</manvolnum></citerefentry> for the next timer
|
|
|
|
iteration, and reenable the timer using
|
|
|
|
<function>sd_event_source_set_enabled()</function>. To calculate
|
|
|
|
the next point in time to pass to
|
|
|
|
<function>sd_event_source_set_time()</function>, either use as
|
|
|
|
base the <parameter>usec</parameter> parameter passed to the timer
|
|
|
|
callback, or the timestamp returned by
|
|
|
|
<function>sd_event_now()</function>. In the former case timer
|
|
|
|
events will be regular, while in the latter case the scheduling
|
|
|
|
latency will keep accumulating on the timer.</para>
|
|
|
|
|
2020-07-28 09:18:08 +00:00
|
|
|
<para><function>sd_event_source_get_time()</function> retrieves the configured time value of an event
|
|
|
|
source created previously with <function>sd_event_add_time()</function> or
|
|
|
|
<function>sd_event_add_time_relative()</function>. It takes the event source object and a pointer to a
|
|
|
|
variable to store the time in, relative to the selected clock's epoch, in µs. The returned value is
|
|
|
|
relative to the epoch, even if the event source was created with a relative time via
|
|
|
|
<function>sd_event_add_time_relative()</function>.</para>
|
|
|
|
|
|
|
|
<para><function>sd_event_source_set_time()</function> changes the time of an event source created
|
|
|
|
previously with <function>sd_event_add_time()</function> or
|
|
|
|
<function>sd_event_add_time_relative()</function>. It takes the event source object and a time relative
|
|
|
|
to the selected clock's epoch, in µs.</para>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2020-07-28 09:18:08 +00:00
|
|
|
<para><function>sd_event_source_set_time_relative()</function> is similar to
|
|
|
|
<function>sd_event_source_set_time()</function>, but takes a time relative to the current time of the
|
|
|
|
event loop iteration, as returned by <function>sd_event_now()</function>.</para>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
|
|
|
<para><function>sd_event_source_get_time_accuracy()</function>
|
2016-07-12 09:58:14 +00:00
|
|
|
retrieves the configured accuracy value of an event source
|
2014-05-06 16:51:08 +00:00
|
|
|
created previously with <function>sd_event_add_time()</function>. It
|
|
|
|
takes the event source object and a pointer to a variable to store
|
2016-01-05 04:17:21 +00:00
|
|
|
the accuracy in. The accuracy is specified in µs.</para>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
|
|
|
<para><function>sd_event_source_set_time_accuracy()</function>
|
|
|
|
changes the configured accuracy of a timer event source created
|
|
|
|
previously with <function>sd_event_add_time()</function>. It takes
|
2016-01-05 04:17:21 +00:00
|
|
|
the event source object and accuracy, in µs.</para>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
|
|
|
<para><function>sd_event_source_get_time_clock()</function>
|
2016-07-12 09:58:14 +00:00
|
|
|
retrieves the configured clock of an event source created
|
2014-05-06 16:51:08 +00:00
|
|
|
previously with <function>sd_event_add_time()</function>. It takes
|
|
|
|
the event source object and a pointer to a variable to store the
|
|
|
|
clock identifier in.</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
|
|
|
|
code. </para>
|
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<refsect2>
|
|
|
|
<title>Errors</title>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<para>Returned values may indicate the following problems:</para>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><constant>-ENOMEM</constant></term>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<listitem><para>Not enough memory to allocate an object.</para></listitem>
|
|
|
|
</varlistentry>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><constant>-EINVAL</constant></term>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<listitem><para>An invalid argument has been passed.</para></listitem>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
</varlistentry>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><constant>-ESTALE</constant></term>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<listitem><para>The event loop is already terminated.</para></listitem>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
</varlistentry>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><constant>-ECHILD</constant></term>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<listitem><para>The event loop has been created in a different process.</para></listitem>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
</varlistentry>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><constant>-EOPNOTSUPP</constant></term>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<listitem><para>The selected clock is not supported by the event loop implementation.</para></listitem>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
</varlistentry>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><constant>-EDOM</constant></term>
|
2014-05-06 16:51:08 +00:00
|
|
|
|
2019-03-21 13:53:00 +00:00
|
|
|
<listitem><para>The passed event source is not a timer event source.</para></listitem>
|
|
|
|
</varlistentry>
|
2020-07-28 09:18:08 +00:00
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><constant>-EOVERFLOW</constant></term>
|
|
|
|
|
|
|
|
<listitem><para>The passed relative time is outside of the allowed range for time values (i.e. the
|
|
|
|
specified value added to the current time is outside the 64 bit unsigned integer range).</para></listitem>
|
|
|
|
</varlistentry>
|
2019-03-21 13:53:00 +00:00
|
|
|
</variablelist>
|
|
|
|
</refsect2>
|
2014-05-06 16:51:08 +00:00
|
|
|
</refsect1>
|
|
|
|
|
2015-11-19 22:38:54 +00:00
|
|
|
<xi:include href="libsystemd-pkgconfig.xml" />
|
|
|
|
|
2014-05-06 16:51:08 +00: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-19 22:38:54 +00:00
|
|
|
<citerefentry><refentrytitle>sd_event_now</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
|
|
|
<citerefentry><refentrytitle>sd_event_add_io</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
2014-09-25 21:27:27 +00:00
|
|
|
<citerefentry><refentrytitle>sd_event_add_signal</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
2014-09-25 21:27:33 +00:00
|
|
|
<citerefentry><refentrytitle>sd_event_add_child</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
2018-05-29 13:59:26 +00:00
|
|
|
<citerefentry><refentrytitle>sd_event_add_inotify</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
2014-09-25 21:27:40 +00:00
|
|
|
<citerefentry><refentrytitle>sd_event_add_defer</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
2015-11-19 22:38:54 +00:00
|
|
|
<citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
|
|
|
<citerefentry><refentrytitle>sd_event_source_set_priority</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
|
|
|
<citerefentry><refentrytitle>sd_event_source_set_userdata</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
|
|
|
<citerefentry><refentrytitle>sd_event_source_set_description</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
2019-11-27 16:11:44 +00:00
|
|
|
<citerefentry><refentrytitle>sd_event_source_set_floating</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
2015-11-19 22:38:54 +00:00
|
|
|
<citerefentry project='man-pages'><refentrytitle>clock_gettime</refentrytitle><manvolnum>2</manvolnum></citerefentry>,
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>timerfd_create</refentrytitle><manvolnum>2</manvolnum></citerefentry>,
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
2014-05-06 16:51:08 +00:00
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
</refentry>
|