Browse Source

Revert all modifications to upstream manpages.

tags/debian-devuan_common
Mark Hindley 3 years ago
parent
commit
6d97c489b9
32 changed files with 364 additions and 213 deletions
  1. +20
    -7
      man/sd_booted.xml
  2. +3
    -3
      man/sd_bus_add_match.xml
  3. +71
    -22
      man/sd_bus_creds_get_pid.xml
  4. +13
    -5
      man/sd_bus_creds_new_from_pid.xml
  5. +4
    -4
      man/sd_bus_default.xml
  6. +4
    -4
      man/sd_bus_error_add_map.xml
  7. +3
    -3
      man/sd_bus_get_fd.xml
  8. +29
    -7
      man/sd_bus_message_append.xml
  9. +3
    -3
      man/sd_bus_message_append_array.xml
  10. +3
    -3
      man/sd_bus_message_append_basic.xml
  11. +3
    -3
      man/sd_bus_message_append_strv.xml
  12. +3
    -3
      man/sd_bus_message_read_basic.xml
  13. +16
    -28
      man/sd_bus_negotiate_fds.xml
  14. +3
    -3
      man/sd_bus_new.xml
  15. +3
    -3
      man/sd_bus_process.xml
  16. +3
    -3
      man/sd_bus_request_name.xml
  17. +3
    -3
      man/sd_bus_track_add_name.xml
  18. +3
    -3
      man/sd_bus_track_new.xml
  19. +3
    -3
      man/sd_event_add_child.xml
  20. +5
    -5
      man/sd_event_add_defer.xml
  21. +3
    -3
      man/sd_event_add_signal.xml
  22. +6
    -6
      man/sd_event_add_time.xml
  23. +6
    -5
      man/sd_event_new.xml
  24. +3
    -3
      man/sd_event_run.xml
  25. +2
    -2
      man/sd_event_source_unref.xml
  26. +19
    -9
      man/sd_event_wait.xml
  27. +53
    -8
      man/sd_is_fifo.xml
  28. +4
    -4
      man/sd_login_monitor_new.xml
  29. +30
    -30
      man/sd_notify.xml
  30. +34
    -6
      man/sd_pid_get_owner_uid.xml
  31. +3
    -16
      man/sd_uid_get_state.xml
  32. +3
    -3
      man/sd_watchdog_enabled.xml

+ 20
- 7
man/sd_booted.xml View File

@@ -11,7 +11,7 @@

<refentryinfo>
<title>sd_booted</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -26,7 +26,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-daemon.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-daemon.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_booted</function></funcdef>
@@ -37,21 +37,34 @@

<refsect1>
<title>Description</title>
<para><function>sd_booted()</function> is a compatibility function
that will always return 0. elogind is not meant to be used on systems
that are booted with systemd. Use systemd-login on such systems.</para>
<para><function>sd_booted()</function> checks whether the system
was booted up using the systemd init system.</para>
</refsect1>

<refsect1>
<title>Return Value</title>

<para>This function always returns zero.</para>
<para>On failure, this call returns a negative errno-style error
code. If the system was booted up with systemd as init system,
this call returns a positive return value, zero otherwise.</para>
</refsect1>

<refsect1>
<title>Notes</title>

<xi:include href="libelogind-pkgconfig.xml" xpointer="pkgconfig-text"/>

<para>Internally, this function checks whether the directory
<filename>/run/systemd/system/</filename> exists. A simple check
like this can also be implemented trivially in shell or any other
language.</para>
</refsect1>

<refsect1>
<title>See Also</title>
<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>
</para>
</refsect1>



+ 3
- 3
man/sd_bus_add_match.xml View File

@@ -12,7 +12,7 @@

<refentryinfo>
<title>sd_bus_add_match</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -31,7 +31,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>typedef int (*<function>sd_bus_message_handler_t</function>)</funcdef>
@@ -163,7 +163,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_slot_unref</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_message_ref</refentrytitle><manvolnum>3</manvolnum></citerefentry>,


+ 71
- 22
man/sd_bus_creds_get_pid.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_bus_creds_get_pid</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -36,6 +36,10 @@
<refname>sd_bus_creds_get_exe</refname>
<refname>sd_bus_creds_get_cmdline</refname>
<refname>sd_bus_creds_get_cgroup</refname>
<refname>sd_bus_creds_get_unit</refname>
<refname>sd_bus_creds_get_slice</refname>
<refname>sd_bus_creds_get_user_unit</refname>
<refname>sd_bus_creds_get_user_slice</refname>
<refname>sd_bus_creds_get_session</refname>
<refname>sd_bus_creds_get_owner_uid</refname>
<refname>sd_bus_creds_has_effective_cap</refname>
@@ -55,7 +59,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_bus_creds_get_pid</function></funcdef>
@@ -159,6 +163,30 @@
<paramdef>const char **<parameter>cgroup</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_bus_creds_get_unit</function></funcdef>
<paramdef>sd_bus_creds *<parameter>c</parameter></paramdef>
<paramdef>const char **<parameter>unit</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_bus_creds_get_slice</function></funcdef>
<paramdef>sd_bus_creds *<parameter>c</parameter></paramdef>
<paramdef>const char **<parameter>slice</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_bus_creds_get_user_unit</function></funcdef>
<paramdef>sd_bus_creds *<parameter>c</parameter></paramdef>
<paramdef>const char **<parameter>unit</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_bus_creds_get_user_slice</function></funcdef>
<paramdef>sd_bus_creds *<parameter>c</parameter></paramdef>
<paramdef>const char **<parameter>slice</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_bus_creds_get_session</function></funcdef>
<paramdef>sd_bus_creds *<parameter>c</parameter></paramdef>
@@ -318,30 +346,51 @@
url="https://www.kernel.org/doc/Documentation/cgroup-v1/cgroups.txt">cgroups.txt</ulink>.
</para>

<para><function>sd_bus_creds_get_unit()</function> will retrieve
the systemd unit name (in the system instance of systemd) that the
process is a part of. See
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. For
processes that are not part of a unit, returns -ENXIO.
</para>

<para><function>sd_bus_creds_get_user_unit()</function> will
retrieve the systemd unit name (in the user instance of systemd)
that the process is a part of. See
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. For
processes that are not part of a user unit, returns -ENXIO.
</para>

<para><function>sd_bus_creds_get_slice()</function> will retrieve
the systemd slice (a unit in the system instance of systemd) that
the process is a part of. See
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Similarly,
<function>sd_bus_creds_get_user_slice()</function> retrieves the
systemd slice of the process, in the user instance of systemd.
</para>

<para><function>sd_bus_creds_get_session()</function> will
retrieve the identifier of the login session that the process is
a part of. See
<citerefentry><refentrytitle>elogind-logind.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>. For
processes that are not part of a session, returns -ENXIO.
</para>
a part of. Please note the login session may be limited to a stub
process or two. User processes may instead be started from their
elogind user manager, e.g. GUI applications started using DBus
activation, as well as service processes which are shared between
multiple logins of the same user. For processes that are not part
of a session, returns -ENXIO.</para>

<para><function>sd_bus_creds_get_owner_uid()</function> will
retrieve the numeric UID (user identifier) of the user who owns
the login session that the process is a part of. See
<citerefentry><refentrytitle>elogind-logind.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
For processes that are not part of a session, returns -ENXIO.
the user unit or login session that the process is a part of. See
<citerefentry><refentrytitle>systemd-logind.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
For processes that are not part of a user unit or session, returns
-ENXIO.
</para>

<para><function>sd_bus_creds_has_effective_cap()</function> will
check whether the capability specified by
<parameter>capability</parameter> was set in the effective
capabilities mask. A positive return value means that is was
set, zero means that it was not set, and a negative return
value indicates an error. See
<citerefentry project='man-pages'><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>
and <varname>Capabilities=</varname> and
<varname>CapabilityBoundingSet=</varname> settings in
<citerefentry><refentrytitle>elogind.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
<para><function>sd_bus_creds_has_effective_cap()</function> will check whether the capability specified by
<parameter>capability</parameter> was set in the effective capabilities mask. A positive return value means that it
was set, zero means that it was not set, and a negative return value indicates an error. See <citerefentry
project='man-pages'><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry> and the
<varname>AmbientCapabilities=</varname> and <varname>CapabilityBoundingSet=</varname> settings in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>

<para><function>sd_bus_creds_has_permitted_cap()</function> is
@@ -435,7 +484,7 @@
<function>sd_bus_creds_get_user_unit()</function>,
<function>sd_bus_creds_get_user_slice()</function>, and
<function>sd_bus_creds_get_session()</function> if the process is
not part of a elogind system unit, systemd user unit, systemd
not part of a systemd system unit, systemd user unit, systemd
slice, or logind session. It will be returned by
<function>sd_bus_creds_get_owner_uid()</function> if the process is
not part of a elogind user unit or logind session. It will also be
@@ -473,7 +522,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_creds_new_from_pid</refentrytitle><manvolnum>2</manvolnum></citerefentry>,
<citerefentry project='man-pages'><refentrytitle>fork</refentrytitle><manvolnum>2</manvolnum></citerefentry>,
@@ -481,7 +530,7 @@
<citerefentry project='man-pages'><refentrytitle>credentials</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry project='man-pages'><refentrytitle>free</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry project='man-pages'><refentrytitle>proc</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>elogind.journal-fields</refentrytitle><manvolnum>7</manvolnum></citerefentry>
<citerefentry><refentrytitle>systemd.journal-fields</refentrytitle><manvolnum>7</manvolnum></citerefentry>
</para>
</refsect1>



+ 13
- 5
man/sd_bus_creds_new_from_pid.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_bus_creds_new_from_pid</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -31,7 +31,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_bus_creds_new_from_pid</function></funcdef>
@@ -42,12 +42,12 @@

<funcprototype>
<funcdef>uint64_t <function>sd_bus_creds_get_mask</function></funcdef>
<paramdef>const sd_bus_creds *<parameter>c</parameter></paramdef>
<paramdef>sd_bus_creds *<parameter>c</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>uint64_t <function>sd_bus_creds_get_augmented_mask</function></funcdef>
<paramdef>const sd_bus_creds *<parameter>c</parameter></paramdef>
<paramdef>sd_bus_creds *<parameter>c</parameter></paramdef>
</funcprototype>

<funcprototype>
@@ -84,6 +84,10 @@
<constant>SD_BUS_CREDS_EXE</constant>,
<constant>SD_BUS_CREDS_CMDLINE</constant>,
<constant>SD_BUS_CREDS_CGROUP</constant>,
<constant>SD_BUS_CREDS_UNIT</constant>,
<constant>SD_BUS_CREDS_SLICE</constant>,
<constant>SD_BUS_CREDS_USER_UNIT</constant>,
<constant>SD_BUS_CREDS_USER_SLICE</constant>,
<constant>SD_BUS_CREDS_SESSION</constant>,
<constant>SD_BUS_CREDS_OWNER_UID</constant>,
<constant>SD_BUS_CREDS_EFFECTIVE_CAPS</constant>,
@@ -134,6 +138,10 @@
<constant>SD_BUS_CREDS_EXE</constant>,
<constant>SD_BUS_CREDS_CMDLINE</constant>,
<constant>SD_BUS_CREDS_CGROUP</constant>,
<constant>SD_BUS_CREDS_UNIT</constant>,
<constant>SD_BUS_CREDS_SLICE</constant>,
<constant>SD_BUS_CREDS_USER_UNIT</constant>,
<constant>SD_BUS_CREDS_USER_SLICE</constant>,
<constant>SD_BUS_CREDS_SESSION</constant>,
<constant>SD_BUS_CREDS_OWNER_UID</constant>,
<constant>SD_BUS_CREDS_EFFECTIVE_CAPS</constant>,
@@ -300,7 +308,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_creds_get_pid</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_get_name_creds</refentrytitle><manvolnum>3</manvolnum></citerefentry>,


+ 4
- 4
man/sd_bus_default.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_bus_default</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -34,7 +34,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_bus_default</function></funcdef>
@@ -274,13 +274,13 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_new</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_ref</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_unref</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry project='die-net'><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>elogind-machined.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd-machined.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
</para>
</refsect1>


+ 4
- 4
man/sd_bus_error_add_map.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_bus_error_add_map</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -29,12 +29,12 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcsynopsisinfo>typedef struct {
const char *name;
int code;
...
} sd_bus_error_map;</funcsynopsisinfo>

</funcsynopsis>
@@ -137,7 +137,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_error</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus-errors</refentrytitle><manvolnum>3</manvolnum></citerefentry>,


+ 3
- 3
man/sd_bus_get_fd.xml View File

@@ -12,7 +12,7 @@

<refentryinfo>
<title>sd_bus_get_fd</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -28,7 +28,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_bus_get_fd</function></funcdef>
@@ -71,7 +71,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_set_fd</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
</para>


+ 29
- 7
man/sd_bus_message_append.xml View File

@@ -11,7 +11,7 @@

<refentryinfo>
<title>sd_bus_message_append</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -21,6 +21,7 @@

<refnamediv>
<refname>sd_bus_message_append</refname>
<refname>sd_bus_message_appendv</refname>

<refpurpose>Attach fields to a D-Bus message based on a type
string</refpurpose>
@@ -28,14 +29,22 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int sd_bus_message_append</funcdef>
<paramdef>sd_bus_message *<parameter>m</parameter></paramdef>
<paramdef>const char *<parameter>types</parameter></paramdef>
<paramdef>...</paramdef>
<paramdef></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int sd_bus_message_appendv</funcdef>
<paramdef>sd_bus_message *<parameter>m</parameter></paramdef>
<paramdef>const char *<parameter>types</parameter></paramdef>
<paramdef>va_list <parameter>ap</parameter></paramdef>
</funcprototype>

</funcsynopsis>
</refsynopsisdiv>

@@ -85,6 +94,14 @@
values for each entry matching the element type of
the dictionary entries.</para>

<para>The <function>sd_bus_message_appendv()</function> is equivalent to
the function <function>sd_bus_message_append()</function>,
except that it is called with a <literal>va_list</literal> instead of
a variable number of arguments. This function does not call the
<function>va_end()</function> macro. Because it invokes the
<function>va_arg()</function> macro, the value of ap
is undefined after the call.</para>

<para>For further details on the D-Bus type system, please consult
the <ulink
url="http://dbus.freedesktop.org/doc/dbus-specification.html#type-system">D-Bus
@@ -145,6 +162,11 @@
</tgroup>
</table>

<para>For types "s" and "g" (unicode string or signature), the pointer may be
<constant>NULL</constant>, which is equivalent to an empty string. See
<citerefentry><refentrytitle>sd_bus_message_append_basic</refentrytitle><manvolnum>3</manvolnum></citerefentry>
for the precise interpretation of those and other types.</para>

</refsect1>

<refsect1>
@@ -169,7 +191,7 @@ dictionary ::= "a" "{" basic_type complete_type "}"
</para>

<programlisting>sd_bus_message *m;
...
sd_bus_message_append(m, "s", "a string");</programlisting>

<para>Append all types of integers:</para>
@@ -209,8 +231,8 @@ sd_bus_message_append(m, "ynqiuxtd", y, n, q, i, u, x, t, d);</programlisting>
<refsect1>
<title>Return Value</title>

<para>On success, this call returns 0 or a positive
integer. On failure, this call returns a negative
<para>On success, these functions return 0 or a positive
integer. On failure, these functions return a negative
errno-style error code.</para>
</refsect1>

@@ -222,7 +244,7 @@ sd_bus_message_append(m, "ynqiuxtd", y, n, q, i, u, x, t, d);</programlisting>
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_message_append_basic</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_message_append_array</refentrytitle><manvolnum>3</manvolnum></citerefentry>


+ 3
- 3
man/sd_bus_message_append_array.xml View File

@@ -11,7 +11,7 @@

<refentryinfo>
<title>sd_bus_message_append_array</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -31,7 +31,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int sd_bus_message_append_array</funcdef>
@@ -169,7 +169,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_message_append</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_message_append_basic</refentrytitle><manvolnum>3</manvolnum></citerefentry>,


+ 3
- 3
man/sd_bus_message_append_basic.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_bus_message_append_basic</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -26,7 +26,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int sd_bus_message_append_basic</funcdef>
@@ -253,7 +253,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_message_append</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<ulink url="http://dbus.freedesktop.org/doc/dbus-specification.html">The D-Bus specification</ulink>


+ 3
- 3
man/sd_bus_message_append_strv.xml View File

@@ -11,7 +11,7 @@

<refentryinfo>
<title>sd_bus_message_append_strv</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -27,7 +27,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int sd_bus_message_append_strv</funcdef>
@@ -73,7 +73,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_message_append</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_message_append_array</refentrytitle><manvolnum>3</manvolnum></citerefentry>,


+ 3
- 3
man/sd_bus_message_read_basic.xml View File

@@ -12,7 +12,7 @@

<refentryinfo>
<title>sd_bus_message_read_basic</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -28,7 +28,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_bus_message_read_basic</function></funcdef>
@@ -84,7 +84,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
</para>
</refsect1>


+ 16
- 28
man/sd_bus_negotiate_fds.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_bus_negotiate_fds</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -28,7 +28,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_bus_negotiate_fds</function></funcdef>
@@ -75,33 +75,21 @@
<citerefentry><refentrytitle>sd_bus_message_get_monotonic_usec</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_message_get_realtime_usec</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_message_get_seqnum</refentrytitle><manvolnum>3</manvolnum></citerefentry>
to query the timestamps of incoming messages. If negotiation is
disabled or not supported, these calls will fail with
<constant>-ENODATA</constant>. Note that not all transports
support timestamping of messages. Specifically, timestamping is
only available on the kdbus transport, but not on dbus1. The
timestamping is applied by the kernel and cannot be manipulated by
userspace. By default, message timestamping is not negotiated for
to query the timestamps of incoming messages. If negotiation is disabled or not supported, these
calls will fail with <constant>-ENODATA</constant>. Note that currently no transports support
timestamping of messages. By default, message timestamping is not negotiated for
connections.</para>

<para><function>sd_bus_negotiate_creds()</function> controls
whether and which implicit sender credentials shall be attached
automatically to all incoming messages. Takes a bus object and a
boolean indicating whether to enable or disable the credential
parts encoded in the bit mask value argument. Note that not all
transports support attaching sender credentials to messages, or do
not support all types of sender credential parameters, or might
suppress them under certain circumstances for individual
messages. Specifically, implicit sender credentials on messages
are only fully supported on kdbus transports, and dbus1 only
supports <constant>SD_BUS_CREDS_UNIQUE_NAME</constant>. The sender
credentials are attached by the kernel and cannot be manipulated
by userspace, and are thus suitable for authorization
decisions. By default, only
<constant>SD_BUS_CREDS_WELL_KNOWN_NAMES</constant> and
<constant>SD_BUS_CREDS_UNIQUE_NAME</constant> are enabled. In
fact, these two credential fields are always sent along and cannot
be turned off.</para>
<para><function>sd_bus_negotiate_creds()</function> controls whether and which implicit sender
credentials shall be attached automatically to all incoming messages. Takes a bus object and a
boolean indicating whether to enable or disable the credential parts encoded in the bit mask
value argument. Note that not all transports support attaching sender credentials to messages,
or do not support all types of sender credential parameters, or might suppress them under
certain circumstances for individual messages. Specifically, dbus1 only supports
<constant>SD_BUS_CREDS_UNIQUE_NAME</constant>. The sender credentials are suitable for
authorization decisions. By default, only <constant>SD_BUS_CREDS_WELL_KNOWN_NAMES</constant> and
<constant>SD_BUS_CREDS_UNIQUE_NAME</constant> are enabled. In fact, these two credential fields
are always sent along and cannot be turned off.</para>

<para>The <function>sd_bus_negotiate_fds()</function> function may
be called only before the connection has been started with
@@ -145,7 +133,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_start</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_message_can_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>,


+ 3
- 3
man/sd_bus_new.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_bus_new</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -29,7 +29,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_bus_new</function></funcdef>
@@ -145,7 +145,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_default_user</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_default_system</refentrytitle><manvolnum>3</manvolnum></citerefentry>,


+ 3
- 3
man/sd_bus_process.xml View File

@@ -12,7 +12,7 @@

<refentryinfo>
<title>sd_bus_process</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -28,7 +28,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_bus_process</function></funcdef>
@@ -82,7 +82,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
</para>
</refsect1>


+ 3
- 3
man/sd_bus_request_name.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_bus_request_name</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -28,7 +28,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_bus_request_name</function></funcdef>
@@ -205,7 +205,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_new</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_slot_unref</refentrytitle><manvolnum>3</manvolnum></citerefentry>


+ 3
- 3
man/sd_bus_track_add_name.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_bus_track_add_name</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -35,7 +35,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_bus_track_add_name</function></funcdef>
@@ -222,7 +222,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_track_new</refentrytitle><manvolnum>3</manvolnum></citerefentry>
</para>


+ 3
- 3
man/sd_bus_track_new.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_bus_track_new</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -34,7 +34,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-bus.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_bus_track_new</function></funcdef>
@@ -224,7 +224,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>
<citerefentry><refentrytitle>sd_bus_track_add_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>
</para>


+ 3
- 3
man/sd_event_add_child.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_event_add_child</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -28,7 +28,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-event.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-event.h&gt;</funcsynopsisinfo>

<funcsynopsisinfo><token>typedef</token> struct sd_event_source sd_event_source;</funcsynopsisinfo>

@@ -203,7 +203,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<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>,
<citerefentry><refentrytitle>sd_event_now</refentrytitle><manvolnum>3</manvolnum></citerefentry>,


+ 5
- 5
man/sd_event_add_defer.xml View File

@@ -10,8 +10,8 @@

<refentryinfo>
<title>sd_event_add_defer</title>
<productname>elogind</productname>
</refentryinfo>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
<refentrytitle>sd_event_add_defer</refentrytitle>
@@ -29,7 +29,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-event.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-event.h&gt;</funcsynopsisinfo>

<funcsynopsisinfo><token>typedef</token> struct sd_event_source sd_event_source;</funcsynopsisinfo>

@@ -129,7 +129,7 @@
<refsect1>
<title>Return Value</title>

<para>On success, this functions return 0 or a positive
<para>On success, these functions return 0 or a positive
integer. On failure, they return a negative errno-style error
code.</para>
</refsect1>
@@ -173,7 +173,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<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>,
<citerefentry><refentrytitle>sd_event_now</refentrytitle><manvolnum>3</manvolnum></citerefentry>,


+ 3
- 3
man/sd_event_add_signal.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_event_add_signal</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -29,7 +29,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-event.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-event.h&gt;</funcsynopsisinfo>

<funcsynopsisinfo><token>typedef</token> struct sd_event_source sd_event_source;</funcsynopsisinfo>

@@ -178,7 +178,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<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>,
<citerefentry><refentrytitle>sd_event_now</refentrytitle><manvolnum>3</manvolnum></citerefentry>,


+ 6
- 6
man/sd_event_add_time.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_event_add_time</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -32,7 +32,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-event.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-event.h&gt;</funcsynopsisinfo>

<funcsynopsisinfo><token>typedef</token> struct sd_event_source sd_event_source;</funcsynopsisinfo>

@@ -99,7 +99,7 @@
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
dispatched. If the paramater is specified as <constant>UINT64_MAX</constant> the timer event will never elapse,
dispatched. If the parameter is specified as <constant>UINT64_MAX</constant> the timer event will never elapse,
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
@@ -189,7 +189,7 @@
in µs.</para>

<para><function>sd_event_source_get_time_accuracy()</function>
retrieves the configured accuracy value of a event source
retrieves the configured accuracy value of an event source
created previously with <function>sd_event_add_time()</function>. It
takes the event source object and a pointer to a variable to store
the accuracy in. The accuracy is specified in µs.</para>
@@ -200,7 +200,7 @@
the event source object and accuracy, in µs.</para>

<para><function>sd_event_source_get_time_clock()</function>
retrieves the configured clock of a event source created
retrieves the configured clock of an event source created
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>
@@ -268,7 +268,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<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>,
<citerefentry><refentrytitle>sd_event_now</refentrytitle><manvolnum>3</manvolnum></citerefentry>,


+ 6
- 5
man/sd_event_new.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_event_new</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -32,7 +32,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-event.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-event.h&gt;</funcsynopsisinfo>

<funcsynopsisinfo><token>typedef</token> struct sd_event sd_event;</funcsynopsisinfo>

@@ -159,8 +159,9 @@
<refsect1>
<title>Return Value</title>

<para>On success, <function>sd_event_new()</function> and
<function>sd_event_default()</function> return 0 or a positive
<para>On success, <function>sd_event_new()</function>,
<function>sd_event_default()</function> and
<function>sd_event_get_tid()</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
@@ -204,7 +205,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<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>,


+ 3
- 3
man/sd_event_run.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_event_run</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -27,7 +27,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-event.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-event.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_event_run</function></funcdef>
@@ -148,7 +148,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_event_new</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>,


+ 2
- 2
man/sd_event_source_unref.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_event_source_unref</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -28,7 +28,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-event.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-event.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>sd_event_source* <function>sd_event_source_unref</function></funcdef>


+ 19
- 9
man/sd_event_wait.xml View File

@@ -10,7 +10,7 @@

<refentryinfo>
<title>sd_event_wait</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -23,6 +23,7 @@
<refname>sd_event_prepare</refname>
<refname>sd_event_dispatch</refname>
<refname>sd_event_get_state</refname>
<refname>sd_event_get_iteration</refname>
<refname>SD_EVENT_INITIAL</refname>
<refname>SD_EVENT_PREPARING</refname>
<refname>SD_EVENT_ARMED</refname>
@@ -36,7 +37,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-event.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-event.h&gt;</funcsynopsisinfo>

<funcsynopsisinfo><token>enum</token> {
<constant>SD_EVENT_INITIAL</constant>,
@@ -69,6 +70,12 @@
<paramdef>sd_event *<parameter>event</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_event_get_iteration</function></funcdef>
<paramdef>sd_event *<parameter>event</parameter></paramdef>
<paramdef>uint64_t *<parameter>ret</parameter></paramdef>
</funcprototype>

</funcsynopsis>
</refsynopsisdiv>

@@ -116,12 +123,15 @@
determine the state the event loop is currently in. It returns one
of the states described below.</para>

<para>All four functions take, as the first argument, the event
loop object <parameter>event</parameter> that has been created
with <function>sd_event_new()</function>. The timeout for
<function>sd_event_wait()</function> is specified in
<parameter>usec</parameter> in milliseconds. <constant>(uint64_t)
-1</constant> may be used to specify an infinite timeout.</para>
<para><function>sd_event_get_iteration()</function> may be used to determine the current iteration of the event
loop. It returns an unsigned 64bit integer containing a counter that increases monotonically with each iteration of
the event loop, starting with 0. The counter is increased at the time of the
<function>sd_event_prepare()</function> invocation.</para>

<para>All five functions take, as the first argument, the event loop object <parameter>event</parameter> that has
been created with <function>sd_event_new()</function>. The timeout for <function>sd_event_wait()</function> is
specified in <parameter>usec</parameter> in microseconds. <constant>(uint64_t) -1</constant> may be used to
specify an infinite timeout.</para>
</refsect1>

<refsect1>
@@ -305,7 +315,7 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_event_new</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>,


+ 53
- 8
man/sd_is_fifo.xml View File

@@ -11,7 +11,7 @@

<refentryinfo>
<title>sd_is_fifo</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -24,13 +24,15 @@
<refname>sd_is_socket</refname>
<refname>sd_is_socket_inet</refname>
<refname>sd_is_socket_unix</refname>
<refname>sd_is_socket_sockaddr</refname>
<refname>sd_is_mq</refname>
<refname>sd_is_special</refname>
<refpurpose>Check the type of a file descriptor</refpurpose>
</refnamediv>

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-daemon.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-daemon.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_is_fifo</function></funcdef>
@@ -55,6 +57,15 @@
<paramdef>uint16_t <parameter>port</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_is_socket_sockaddr</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>type</parameter></paramdef>
<paramdef>const struct sockaddr *<parameter>addr</parameter></paramdef>
<paramdef>unsigned <parameter>addr_len</parameter></paramdef>
<paramdef>int <parameter>listening</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_is_socket_unix</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
@@ -64,6 +75,12 @@
<paramdef>size_t <parameter>length</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_is_mq</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>const char *<parameter>path</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_is_special</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
@@ -86,11 +103,11 @@
whether the specified file descriptor refers to a socket. If the
<parameter>family</parameter> parameter is not
<constant>AF_UNSPEC</constant>, it is checked whether the socket
is of the specified family (AF_UNIX, <constant>AF_INET</constant>,
...). If the <parameter>type</parameter> parameter is not 0, it is
checked whether the socket is of the specified type
(<constant>SOCK_STREAM</constant>,
<constant>SOCK_DGRAM</constant>, ...). If the
is of the specified family (<constant>AF_UNIX</constant>,
<constant>AF_INET</constant>, …). If the <parameter>type</parameter>
parameter is not 0, it is checked whether the socket is of the
specified type (<constant>SOCK_STREAM</constant>,
<constant>SOCK_DGRAM</constant>, ). If the
<parameter>listening</parameter> parameter is positive, it is
checked whether the socket is in accepting mode, i.e.
<function>listen()</function> has been called for it. If
@@ -108,6 +125,18 @@
<constant>AF_UNSPEC</constant>, <constant>AF_INET</constant>, or
<constant>AF_INET6</constant>.</para>

<para><function>sd_is_socket_sockaddr()</function> is similar to
<function>sd_is_socket_inet()</function>, but checks if the socket is bound to the
address specified by <parameter>addr</parameter>. The
<structfield>family</structfield> specified by <parameter>addr</parameter> must be
either <constant>AF_INET</constant> or <constant>AF_INET6</constant> and
<parameter>addr_len</parameter> must be large enough for that family. If
<parameter>addr</parameter> specifies a non-zero port, it is also checked if the
socket is bound to this port. In addition, for IPv6, if <parameter>addr</parameter>
specifies non-zero <structfield>sin6_flowinfo</structfield> or
<structfield>sin6_scope_id</structfield>, it is checked if the socket has the same
values.</para>

<para><function>sd_is_socket_unix()</function> is similar to
<function>sd_is_socket()</function> but optionally checks the
<constant>AF_UNIX</constant> path the socket is bound to, unless
@@ -120,6 +149,12 @@
<parameter>path</parameter> to the initial 0 byte of the socket
address.</para>

<para><function>sd_is_mq()</function> may be called to check
whether the specified file descriptor refers to a POSIX message
queue. If the <parameter>path</parameter> parameter is not
<constant>NULL</constant>, it is checked whether the message queue
is bound to the specified name.</para>

<para><function>sd_is_special()</function> may be called to check
whether the specified file descriptor refers to a special file. If
the <parameter>path</parameter> parameter is not
@@ -152,7 +187,17 @@
<refsect1>
<title>See Also</title>
<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_listen_fds</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry project='man-pages'><refentrytitle>ip</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry project='man-pages'><refentrytitle>ipv6</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry project='man-pages'><refentrytitle>unix</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry project='man-pages'><refentrytitle>fifo</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry project='man-pages'><refentrytitle>mq_overview</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry project='man-pages'><refentrytitle>socket</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
</para>
</refsect1>



+ 4
- 4
man/sd_login_monitor_new.xml View File

@@ -11,7 +11,7 @@

<refentryinfo>
<title>sd_login_monitor_new</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -33,7 +33,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-login.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-login.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_login_monitor_new</function></funcdef>
@@ -180,7 +180,7 @@ if (t == (uint64_t) -1)
else {
struct timespec ts;
uint64_t n;
clock_getttime(CLOCK_MONOTONIC, &amp;ts);
clock_gettime(CLOCK_MONOTONIC, &amp;ts);
n = (uint64_t) ts.tv_sec * 1000000 + ts.tv_nsec / 1000;
msec = t > n ? (int) ((t - n + 999) / 1000) : 0;
}</programlisting>
@@ -240,7 +240,7 @@ else {
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-login</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_get_seats</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>poll</refentrytitle><manvolnum>2</manvolnum></citerefentry>,


+ 30
- 30
man/sd_notify.xml View File

@@ -169,7 +169,7 @@
watchdog timestamp. This is the keep-alive ping that services
need to issue in regular intervals if
<varname>WatchdogSec=</varname> is enabled for it. See
<citerefentry><refentrytitle>elogind.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for information how to enable this functionality and
<citerefentry><refentrytitle>sd_watchdog_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>
for the details of how the service can check whether the
@@ -200,25 +200,24 @@
<varlistentry>
<term>FDSTORE=1</term>

<listitem><para>Stores additional file descriptors in the service manager. File
descriptors sent this way will be maintained per-service by the service manager
and will be passed again using the usual file descriptor passing logic on the next
invocation of the service, see
<citerefentry><refentrytitle>sd_listen_fds</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
This is useful for implementing service restart schemes where services serialize
their state to <filename>/run</filename>, push their file descriptors to the
system manager, and are then restarted, retrieving their state again via socket
passing and <filename>/run</filename>. Note that the service manager will accept
messages for a service only if <varname>FileDescriptorStoreMax=</varname> is set
to non-zero for it (defaults to zero, see
<citerefentry><refentrytitle>elogind.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
File descriptors must be pollable, see
<citerefentry><refentrytitle>epoll_ctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>.
Multiple arrays of file descriptors may be sent in separate messages, in which
case the arrays are combined. Note that the service manager removes duplicate
file descriptors before passing them to the service. Use
<function>sd_pid_notify_with_fds()</function> to send messages with
<literal>FDSTORE=1</literal>, see below.</para></listitem>
<listitem><para>Stores additional file descriptors in the service manager. File descriptors sent this way will
be maintained per-service by the service manager and will later be handed back using the usual file descriptor
passing logic at the next invocation of the service, see
<citerefentry><refentrytitle>sd_listen_fds</refentrytitle><manvolnum>3</manvolnum></citerefentry>. This is
useful for implementing services that can restart after an explicit request or a crash without losing
state. Any open sockets and other file descriptors which should not be closed during the restart may be stored
this way. Application state can either be serialized to a file in <filename>/run</filename>, or better, stored
in a <citerefentry><refentrytitle>memfd_create</refentrytitle><manvolnum>2</manvolnum></citerefentry> memory
file descriptor. Note that the service manager will accept messages for a service only if its
<varname>FileDescriptorStoreMax=</varname> setting is non-zero (defaults to zero, see
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>). If file
descriptors sent are pollable (see
<citerefentry><refentrytitle>epoll_ctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>), then any
<constant>EPOLLHUP</constant> or <constant>EPOLLERR</constant> event seen on them will result in their
automatic removal from the store. Multiple arrays of file descriptors may be sent in separate messages, in
which case the arrays are combined. Note that the service manager removes duplicate (pointing to the same
object) file descriptors before passing them to the service. Use <function>sd_pid_notify_with_fds()</function>
to send messages with <literal>FDSTORE=1</literal>, see below.</para></listitem>
</varlistentry>

<varlistentry>
@@ -252,7 +251,7 @@
<para>Note that elogind will accept status data sent from a
service only if the <varname>NotifyAccess=</varname> option is
correctly set in the service definition file. See
<citerefentry><refentrytitle>elogind.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details.</para>

<para>Note that <function>sd_notify()</function> notifications may be attributed to units correctly only if either
@@ -299,13 +298,14 @@
<refsect1>
<title>Return Value</title>

<para>On failure, these calls return a negative errno-style error
code. If <varname>$NOTIFY_SOCKET</varname> was not set and hence
no status data could be sent, 0 is returned. If the status was
sent, these functions return with a positive return value. In
order to support both, init systems that implement this scheme and
those which do not, it is generally recommended to ignore the
return value of this call.</para>
<para>On failure, these calls return a negative errno-style error code. If <varname>$NOTIFY_SOCKET</varname> was
not set and hence no status message could be sent, 0 is returned. If the status was sent, these functions return a
positive value. In order to support both service managers that implement this scheme and those which do not, it is
generally recommended to ignore the return value of this call. Note that the return value simply indicates whether
the notification message was enqueued properly, it does not reflect whether the message could be processed
successfully. Specifically, no error is returned when a file descriptor is attempted to be stored using
<varname>FDSTORE=1</varname> but the service is not actually configured to permit storing of file descriptors (see
above).</para>
</refsect1>

<refsect1>
@@ -388,13 +388,13 @@
<refsect1>
<title>See Also</title>
<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_listen_fds</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_listen_fds_with_names</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_watchdog_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>daemon</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry><refentrytitle>elogind.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
</para>
</refsect1>



+ 34
- 6
man/sd_pid_get_owner_uid.xml View File

@@ -11,7 +11,7 @@

<refentryinfo>
<title>sd_pid_get_owner_uid</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -25,12 +25,16 @@
<refname>sd_pid_get_user_unit</refname>
<refname>sd_pid_get_unit</refname>
<refname>sd_pid_get_machine_name</refname>
<refname>sd_pid_get_slice</refname>
<refname>sd_pid_get_user_slice</refname>
<refname>sd_pid_get_cgroup</refname>
<refname>sd_peer_get_owner_uid</refname>
<refname>sd_peer_get_session</refname>
<refname>sd_peer_get_user_unit</refname>
<refname>sd_peer_get_unit</refname>
<refname>sd_peer_get_machine_name</refname>
<refname>sd_peer_get_slice</refname>
<refname>sd_peer_get_user_slice</refname>
<refname>sd_peer_get_cgroup</refname>
<refpurpose>Determine the owner uid of the user unit or session,
or the session, user unit, system unit, container/VM or slice that
@@ -39,7 +43,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-login.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-login.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_pid_get_owner_uid</function></funcdef>
@@ -71,6 +75,18 @@
<paramdef>char **<parameter>name</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_pid_get_slice</function></funcdef>
<paramdef>pid_t <parameter>pid</parameter></paramdef>
<paramdef>char **<parameter>slice</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_pid_get_user_slice</function></funcdef>
<paramdef>pid_t <parameter>pid</parameter></paramdef>
<paramdef>char **<parameter>slice</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_pid_get_cgroup</function></funcdef>
<paramdef>pid_t <parameter>pid</parameter></paramdef>
@@ -107,6 +123,18 @@
<paramdef>char **<parameter>name</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_peer_get_slice</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>char **<parameter>slice</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_peer_get_user_slice</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>char **<parameter>slice</parameter></paramdef>
</funcprototype>

<funcprototype>
<funcdef>int <function>sd_peer_get_cgroup</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
@@ -236,7 +264,7 @@
</varlistentry>

<varlistentry>
<term><constant>-BADF</constant></term>
<term><constant>-EBADF</constant></term>

<listitem><para>The specified socket file descriptor was
invalid.</para></listitem>
@@ -281,12 +309,12 @@
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-login</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_session_is_active</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>getsid</refentrytitle><manvolnum>2</manvolnum></citerefentry>,
<citerefentry><refentrytitle>elogind.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>elogind-machined.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd-machined.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
</para>
</refsect1>



+ 3
- 16
man/sd_uid_get_state.xml View File

@@ -11,7 +11,7 @@

<refentryinfo>
<title>sd_uid_get_state</title>
<productname>elogind</productname>
<productname>systemd</productname>
</refentryinfo>

<refmeta>
@@ -30,7 +30,7 @@

<refsynopsisdiv>
<funcsynopsis>
<funcsynopsisinfo>#include &lt;elogind/sd-login.h&gt;</funcsynopsisinfo>
<funcsynopsisinfo>#include &lt;systemd/sd-login.h&gt;</funcsynopsisinfo>

<funcprototype>
<funcdef>int <function>sd_uid_get_state</function></funcdef>
@@ -187,24 +187,11 @@

<xi:include href="libelogind-pkgconfig.xml" />

<refsect1>
<title>History</title>

<para><function>sd_uid_get_state()</function>,
<function>sd_uid_is_on_seat()</function>,
<function>sd_uid_get_sessions()</function>, and
<function>sd_uid_get_seats()</function> functions were added in
elogind-31.</para>

<para><function>sd_uid_get_display()</function> was added in
elogind-213.</para>
</refsect1>

<refsect1>
<title>See Also</title>

<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-login</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_pid_get_owner_uid</refentrytitle><manvolnum>3</manvolnum></citerefentry>
</para>


+ 3
- 3
man/sd_watchdog_enabled.xml View File

@@ -72,7 +72,7 @@

<para>To enable service supervision with the watchdog logic, use
<varname>WatchdogSec=</varname> in service files. See
<citerefentry><refentrytitle>elogind.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details.</para>

<para>Use
@@ -133,10 +133,10 @@
<refsect1>
<title>See Also</title>
<para>
<citerefentry><refentrytitle>elogind</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>daemon</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry><refentrytitle>elogind.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_notify</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_event_set_watchdog</refentrytitle><manvolnum>3</manvolnum></citerefentry>
</para>


Loading…
Cancel
Save