2014-11-21 19:44:48 +00:00
|
|
|
|
<?xml version='1.0'?> <!--*- Mode: nxml; nxml-child-indent: 2; indent-tabs-mode: nil -*-->
|
2014-04-01 17:12:59 +00:00
|
|
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
|
2015-06-18 17:47:44 +00:00
|
|
|
|
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
|
2014-04-01 17:12:59 +00:00
|
|
|
|
|
|
|
|
|
<!--
|
2015-02-11 04:19:26 +00:00
|
|
|
|
This file is part of systemd.
|
2014-04-01 17:12:59 +00:00
|
|
|
|
|
2015-02-11 04:19:26 +00:00
|
|
|
|
Copyright 2014 Lennart Poettering
|
2014-04-01 17:12:59 +00:00
|
|
|
|
|
2015-02-11 04:19:26 +00:00
|
|
|
|
systemd is free software; you can redistribute it and/or modify it
|
|
|
|
|
under the terms of the GNU Lesser General Public License as published by
|
|
|
|
|
the Free Software Foundation; either version 2.1 of the License, or
|
|
|
|
|
(at your option) any later version.
|
2014-04-01 17:12:59 +00:00
|
|
|
|
|
2015-02-11 04:19:26 +00:00
|
|
|
|
systemd is distributed in the hope that it will be useful, but
|
|
|
|
|
WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
|
Lesser General Public License for more details.
|
2014-04-01 17:12:59 +00:00
|
|
|
|
|
2015-02-11 04:19:26 +00:00
|
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
|
|
|
|
along with systemd; If not, see <http://www.gnu.org/licenses/>.
|
2014-04-01 17:12:59 +00:00
|
|
|
|
-->
|
|
|
|
|
|
2015-06-17 10:32:33 +00:00
|
|
|
|
<refentry id="sd_event_new">
|
2014-04-01 17:12:59 +00:00
|
|
|
|
|
|
|
|
|
<refentryinfo>
|
|
|
|
|
<title>sd_event_new</title>
|
|
|
|
|
<productname>systemd</productname>
|
|
|
|
|
|
|
|
|
|
<authorgroup>
|
|
|
|
|
<author>
|
|
|
|
|
<contrib>Developer</contrib>
|
|
|
|
|
<firstname>Lennart</firstname>
|
|
|
|
|
<surname>Poettering</surname>
|
|
|
|
|
<email>lennart@poettering.net</email>
|
|
|
|
|
</author>
|
|
|
|
|
</authorgroup>
|
|
|
|
|
</refentryinfo>
|
|
|
|
|
|
|
|
|
|
<refmeta>
|
|
|
|
|
<refentrytitle>sd_event_new</refentrytitle>
|
|
|
|
|
<manvolnum>3</manvolnum>
|
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
|
|
<refnamediv>
|
|
|
|
|
<refname>sd_event_new</refname>
|
|
|
|
|
<refname>sd_event_default</refname>
|
|
|
|
|
<refname>sd_event_ref</refname>
|
|
|
|
|
<refname>sd_event_unref</refname>
|
|
|
|
|
|
|
|
|
|
<refpurpose>Acquire and release an event loop object</refpurpose>
|
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
|
|
|
|
<funcsynopsis>
|
|
|
|
|
<funcsynopsisinfo>#include <systemd/sd-bus.h></funcsynopsisinfo>
|
|
|
|
|
|
|
|
|
|
<funcprototype>
|
|
|
|
|
<funcdef>int <function>sd_event_new</function></funcdef>
|
|
|
|
|
<paramdef>sd_bus **<parameter>event</parameter></paramdef>
|
|
|
|
|
</funcprototype>
|
|
|
|
|
|
|
|
|
|
<funcprototype>
|
|
|
|
|
<funcdef>int <function>sd_event_default</function></funcdef>
|
|
|
|
|
<paramdef>sd_bus **<parameter>event</parameter></paramdef>
|
|
|
|
|
</funcprototype>
|
|
|
|
|
|
|
|
|
|
<funcprototype>
|
|
|
|
|
<funcdef>sd_bus *<function>sd_event_ref</function></funcdef>
|
|
|
|
|
<paramdef>sd_bus *<parameter>event</parameter></paramdef>
|
|
|
|
|
</funcprototype>
|
|
|
|
|
|
|
|
|
|
<funcprototype>
|
|
|
|
|
<funcdef>sd_bus *<function>sd_event_unref</function></funcdef>
|
|
|
|
|
<paramdef>sd_bus *<parameter>event</parameter></paramdef>
|
|
|
|
|
</funcprototype>
|
|
|
|
|
|
|
|
|
|
</funcsynopsis>
|
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Description</title>
|
|
|
|
|
|
|
|
|
|
<para><function>sd_event_new()</function> allocates a new event
|
|
|
|
|
loop object. The event loop object is returned in the
|
2014-05-07 23:28:45 +00:00
|
|
|
|
<parameter>event</parameter> parameter. After use, drop
|
2014-04-01 17:12:59 +00:00
|
|
|
|
the returned reference with
|
|
|
|
|
<function>sd_event_unref()</function>. When the last reference is
|
2014-09-25 21:27:17 +00:00
|
|
|
|
dropped, the object is freed.</para>
|
2014-04-01 17:12:59 +00:00
|
|
|
|
|
|
|
|
|
<para><function>sd_event_default()</function> acquires a reference
|
|
|
|
|
to the default event loop object of the calling thread, possibly
|
|
|
|
|
allocating a new object if no default event loop object has been
|
2014-05-07 23:28:45 +00:00
|
|
|
|
allocated yet for the thread. After use, drop the returned
|
2014-04-14 17:12:45 +00:00
|
|
|
|
reference with <function>sd_event_unref()</function>. When the
|
2014-05-07 23:28:45 +00:00
|
|
|
|
last reference is dropped, the event loop is freed. If this
|
2014-04-01 17:12:59 +00:00
|
|
|
|
function is called while the object returned from a previous call
|
|
|
|
|
from the same thread is still referenced, the same object is
|
|
|
|
|
returned again, but the reference is increased by one. It is
|
|
|
|
|
recommended to use this call instead of
|
|
|
|
|
<function>sd_event_new()</function> in order to share event loop
|
|
|
|
|
objects between various components that are dispatched in the same
|
2014-09-25 21:27:17 +00:00
|
|
|
|
thread. All threads have exactly either zero or one default event loop
|
|
|
|
|
objects associated, but never more.</para>
|
2014-04-01 17:12:59 +00:00
|
|
|
|
|
|
|
|
|
<para><function>sd_event_ref()</function> increases the reference
|
2014-09-25 21:27:17 +00:00
|
|
|
|
count of the specified event loop object by one.</para>
|
2014-04-01 17:12:59 +00:00
|
|
|
|
|
|
|
|
|
<para><function>sd_event_unref()</function> decreases the
|
2014-09-25 21:27:17 +00:00
|
|
|
|
reference count of the specified event loop object by one. If
|
|
|
|
|
the count hits zero, the object is freed. Note that it
|
2014-05-07 23:28:44 +00:00
|
|
|
|
is freed regardless of whether it is the default event loop object for a
|
2014-04-01 17:12:59 +00:00
|
|
|
|
thread or not. This means that allocating an event loop with
|
2014-05-07 23:28:45 +00:00
|
|
|
|
<function>sd_event_default()</function>, then releasing it, and
|
2014-04-01 17:12:59 +00:00
|
|
|
|
then acquiring a new one with
|
|
|
|
|
<function>sd_event_default()</function> will result in two
|
2014-09-25 21:27:17 +00:00
|
|
|
|
distinct objects. Note that in order to free an event loop object,
|
2014-04-01 17:12:59 +00:00
|
|
|
|
all remaining event sources of the event loop also need to be
|
2014-09-25 21:27:17 +00:00
|
|
|
|
freed as each keeps a reference to it.</para>
|
2014-04-01 17:12:59 +00:00
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Return Value</title>
|
|
|
|
|
|
|
|
|
|
<para>On success, <function>sd_event_new()</function> and
|
|
|
|
|
<function>sd_event_default()</function> return 0 or a positive
|
|
|
|
|
integer. On failure, they return a negative errno-style error
|
|
|
|
|
code. <function>sd_event_ref()</function> always returns a pointer
|
|
|
|
|
to the event loop object passed
|
|
|
|
|
in. <function>sd_event_unref()</function> always returns
|
2014-09-25 21:27:17 +00:00
|
|
|
|
<constant>NULL</constant>.</para>
|
2014-04-01 17:12:59 +00:00
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Errors</title>
|
|
|
|
|
|
|
|
|
|
<para>Returned errors may indicate the following problems:</para>
|
|
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
|
<varlistentry>
|
2014-09-25 21:27:46 +00:00
|
|
|
|
<term><constant>-ENOMEM</constant></term>
|
2014-04-01 17:12:59 +00:00
|
|
|
|
|
2014-09-25 21:27:17 +00:00
|
|
|
|
<listitem><para>Not enough memory to allocate the object.</para></listitem>
|
2014-04-01 17:12:59 +00:00
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
2014-09-25 21:27:46 +00:00
|
|
|
|
<term><constant>-EMFILE</constant></term>
|
2014-04-01 17:12:59 +00:00
|
|
|
|
|
|
|
|
|
<listitem><para>The maximum number of event loops has been allocated.</para></listitem>
|
|
|
|
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
</variablelist>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Notes</title>
|
|
|
|
|
|
|
|
|
|
<para><function>sd_event_new()</function> and the other functions
|
|
|
|
|
described here are available as a shared library, which can be
|
|
|
|
|
compiled and linked to with the
|
man: add a mapping for external manpages
It is annoying when we have dead links on fd.o.
Add project='man-pages|die-net|archlinux' to <citerefentry>-ies.
In generated html, add external links to
http://man7.org/linux/man-pages/man, http://linux.die.net/man/,
https://www.archlinux.org/.
By default, pages in sections 2 and 4 go to man7, since Michael
Kerrisk is the autorative source on kernel related stuff.
The rest of links goes to linux.die.net, because they have the
manpages.
Except for the pacman stuff, since it seems to be only available from
archlinux.org.
Poor gummiboot gets no link, because gummitboot(8) ain't to be found
on the net. According to common wisdom, that would mean that it does
not exist. But I have seen Kay using it, so I know it does, and
deserves to be found. Can somebody be nice and put it up somewhere?
2014-07-07 22:25:54 +00:00
|
|
|
|
<constant>libsystemd</constant> <citerefentry project='die-net'><refentrytitle>pkg-config</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
2014-04-01 17:12:59 +00:00
|
|
|
|
file.</para>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<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_add_io</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>sd_event_add_time</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>sd_event_add_signal</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>sd_event_add_child</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>sd_event_add_defer</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>sd_event_add_post</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>sd_event_add_exit</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
|
|
|
|
</para>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
</refentry>
|