man: adjust indentation

This commit is contained in:
David Tardon 2023-12-24 10:46:55 +01:00
parent 74512bbc38
commit 7e59b569a1
3 changed files with 19 additions and 19 deletions

View File

@ -8,10 +8,10 @@
<refsect1>
<title/>
<para id="singular">This option cannot be bypassed by prefixing <literal>+</literal> to the executable path
in the service unit, as it applies to the whole control group.</para>
<para id="singular">This option cannot be bypassed by prefixing <literal>+</literal> to the executable path
in the service unit, as it applies to the whole control group.</para>
<para id="plural">These options cannot be bypassed by prefixing <literal>+</literal> to the executable path
in the service unit, as it applies to the whole control group.</para>
<para id="plural">These options cannot be bypassed by prefixing <literal>+</literal> to the executable path
in the service unit, as it applies to the whole control group.</para>
</refsect1>

View File

@ -8,8 +8,8 @@
<refsect1>
<title/>
<para id="controllers-text">The following controller names may be specified: <option>cpu</option>, <option>cpuacct</option>,
<option>cpuset</option>, <option>io</option>, <option>blkio</option>, <option>memory</option>, <option>devices</option>,
<option>pids</option>, <option>bpf-firewall</option>, and <option>bpf-devices</option>.</para>
<para id="controllers-text">The following controller names may be specified: <option>cpu</option>, <option>cpuacct</option>,
<option>cpuset</option>, <option>io</option>, <option>blkio</option>, <option>memory</option>, <option>devices</option>,
<option>pids</option>, <option>bpf-firewall</option>, and <option>bpf-devices</option>.</para>
</refsect1>

View File

@ -6,19 +6,19 @@
<refsect1>
<title/>
<para id="strict">All functions listed here are thread-agnostic and only a single specific thread may operate on a
given object during its entire lifetime. It's safe to allocate multiple independent objects and use each from a
specific thread in parallel. However, it's not safe to allocate such an object in one thread, and operate or free it
from any other, even if locking is used to ensure these threads don't operate on it at the very same time.</para>
<para id="strict">All functions listed here are thread-agnostic and only a single specific thread may operate on a
given object during its entire lifetime. It's safe to allocate multiple independent objects and use each from a
specific thread in parallel. However, it's not safe to allocate such an object in one thread, and operate or free it
from any other, even if locking is used to ensure these threads don't operate on it at the very same time.</para>
<para id="safe">All functions listed here are thread-safe and may be called in parallel from multiple threads.</para>
<para id="safe">All functions listed here are thread-safe and may be called in parallel from multiple threads.</para>
<para id='getenv'>The code described here uses
<citerefentry project='man-pages'><refentrytitle>getenv</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
which is declared to be not multi-thread-safe. This means that the code calling the functions described
here must not call
<citerefentry project='man-pages'><refentrytitle>setenv</refentrytitle><manvolnum>3</manvolnum></citerefentry>
from a parallel thread. It is recommended to only do calls to <function>setenv()</function>
from an early phase of the program when no other threads have been started.</para>
<para id='getenv'>The code described here uses
<citerefentry project='man-pages'><refentrytitle>getenv</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
which is declared to be not multi-thread-safe. This means that the code calling the functions described
here must not call
<citerefentry project='man-pages'><refentrytitle>setenv</refentrytitle><manvolnum>3</manvolnum></citerefentry>
from a parallel thread. It is recommended to only do calls to <function>setenv()</function>
from an early phase of the program when no other threads have been started.</para>
</refsect1>