summaryrefslogtreecommitdiff
path: root/man/sd_event_run.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2019-03-21 14:53:00 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2019-03-21 14:53:00 +0100
commitb1de39dec8e9acd875e2038e418d7193fb380b41 (patch)
treea044b2ad47d393f4f0439462122e5a9ba129b5b1 /man/sd_event_run.xml
parent6d99c5d1d9832a2a85c77f8d90767028651f3f35 (diff)
downloadsystemd-b1de39dec8e9acd875e2038e418d7193fb380b41.tar.gz
man: make separate "Errors" sections subsection of "Return value"
Logically, this is better, because we're describing a subset of possible return values. Visually this also looks quite good because groff renders refsect2 much less prominently. Also rewrap things, add <constant> in various places, fix some typos.
Diffstat (limited to 'man/sd_event_run.xml')
-rw-r--r--man/sd_event_run.xml54
1 files changed, 27 insertions, 27 deletions
diff --git a/man/sd_event_run.xml b/man/sd_event_run.xml
index 245df3cd22..5c33d61fdf 100644
--- a/man/sd_event_run.xml
+++ b/man/sd_event_run.xml
@@ -96,47 +96,47 @@
dispatched. <function>sd_event_loop()</function> returns the exit
code specified when invoking
<function>sd_event_exit()</function>.</para>
- </refsect1>
- <refsect1>
- <title>Errors</title>
+ <refsect2>
+ <title>Errors</title>
- <para>Returned errors may indicate the following problems:</para>
+ <para>Returned errors may indicate the following problems:</para>
- <variablelist>
- <varlistentry>
- <term><constant>-EINVAL</constant></term>
+ <variablelist>
+ <varlistentry>
+ <term><constant>-EINVAL</constant></term>
- <listitem><para>The <parameter>event</parameter> parameter is
- invalid or <constant>NULL</constant>.</para></listitem>
- </varlistentry>
+ <listitem><para>The <parameter>event</parameter> parameter is invalid or
+ <constant>NULL</constant>.</para></listitem>
+ </varlistentry>
- <varlistentry>
- <term><constant>-EBUSY</constant></term>
+ <varlistentry>
+ <term><constant>-EBUSY</constant></term>
- <listitem><para>The event loop object is not in the right
- state (see
- <citerefentry><refentrytitle>sd_event_prepare</refentrytitle><manvolnum>3</manvolnum></citerefentry>
- for an explanation of possible states).</para></listitem>
- </varlistentry>
+ <listitem><para>The event loop object is not in the right
+ state (see
+ <citerefentry><refentrytitle>sd_event_prepare</refentrytitle><manvolnum>3</manvolnum></citerefentry>
+ for an explanation of possible states).</para></listitem>
+ </varlistentry>
- <varlistentry>
- <term><constant>-ESTALE</constant></term>
+ <varlistentry>
+ <term><constant>-ESTALE</constant></term>
- <listitem><para>The event loop is already terminated.</para></listitem>
+ <listitem><para>The event loop is already terminated.</para></listitem>
- </varlistentry>
+ </varlistentry>
- <varlistentry>
- <term><constant>-ECHILD</constant></term>
+ <varlistentry>
+ <term><constant>-ECHILD</constant></term>
- <listitem><para>The event loop has been created in a different process.</para></listitem>
+ <listitem><para>The event loop has been created in a different process.</para></listitem>
- </varlistentry>
+ </varlistentry>
- </variablelist>
+ </variablelist>
- <para>Other errors are possible, too.</para>
+ <para>Other errors are possible, too.</para>
+ </refsect2>
</refsect1>
<xi:include href="libsystemd-pkgconfig.xml" />