diff options
42 files changed, 73 insertions, 73 deletions
diff --git a/man/halt.xml b/man/halt.xml index 2a13d3c635..f54a8648ad 100644 --- a/man/halt.xml +++ b/man/halt.xml @@ -148,7 +148,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/hostnamectl.xml b/man/hostnamectl.xml index 29914b8c8d..4bc05f52ce 100644 --- a/man/hostnamectl.xml +++ b/man/hostnamectl.xml @@ -255,7 +255,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/journalctl.xml b/man/journalctl.xml index 2de72523cc..6a972109c5 100644 --- a/man/journalctl.xml +++ b/man/journalctl.xml @@ -691,7 +691,7 @@ matching <replaceable>GLOB</replaceable> instead of the default runtime and system journal paths. May be specified - multiple times, in which case, files will + multiple times, in which case files will be suitably interleaved.</para></listitem> </varlistentry> diff --git a/man/sd-daemon.xml b/man/sd-daemon.xml index 74fe435ac4..ed85debd77 100644 --- a/man/sd-daemon.xml +++ b/man/sd-daemon.xml @@ -83,7 +83,7 @@ <citerefentry><refentrytitle>sd_booted</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_is_fifo</refentrytitle><manvolnum>3</manvolnum></citerefentry> for more information about the functions - implemented. In addition to these functions a couple + implemented. In addition to these functions, a couple of logging prefixes are defined as macros:</para> <programlisting>#define SD_EMERG "<0>" /* system is unusable */ @@ -135,7 +135,7 @@ implementation. See the respective function man pages for details.</para> - <para>In addition, for details about the algorithms + <para>In addition, for details about the algorithms, check the liberally licensed reference implementation sources: <ulink url="http://cgit.freedesktop.org/systemd/systemd/plain/src/libsystemd-daemon/sd-daemon.c"/> diff --git a/man/sd-readahead.xml b/man/sd-readahead.xml index f8a0a0b559..bcc46b24d8 100644 --- a/man/sd-readahead.xml +++ b/man/sd-readahead.xml @@ -83,7 +83,7 @@ reference implementation. See the respective function man pages for details.</para> - <para>In addition, for details about the algorithms + <para>In addition, for details about the algorithms, check the liberally licensed reference implementation sources: <ulink url="http://cgit.freedesktop.org/systemd/systemd/plain/src/readahead/sd-readahead.c"/> diff --git a/man/sd_booted.xml b/man/sd_booted.xml index 6f8cc95ca7..1e38d2abd3 100644 --- a/man/sd_booted.xml +++ b/man/sd_booted.xml @@ -106,7 +106,7 @@ file. Alternatively, applications consuming these APIs may copy the implementation into their source tree. For more details about the reference - implementation see + implementation, see <citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para> <para>If the reference implementation is used as diff --git a/man/sd_bus_message_get_cookie.xml b/man/sd_bus_message_get_cookie.xml index db344bf1be..0e3c4ba723 100644 --- a/man/sd_bus_message_get_cookie.xml +++ b/man/sd_bus_message_get_cookie.xml @@ -78,7 +78,7 @@ <para><function>sd_bus_message_get_reply_cookie()</function> returns the transaction cookie of the message the specified message is a response to. When a reply - message is generated for a method call message its + message is generated for a method call message, its cookie is copied over into this field. Note that while every message that is transferred is identified by a cookie, only response messages carry a reply cookie @@ -96,7 +96,7 @@ integer. On failure, these calls return a negative errno-style error code.</para> - <para>On success the cookie/reply cookie is returned + <para>On success, the cookie/reply cookie is returned in the specified 64bit unsigned integer variable.</para> </refsect1> diff --git a/man/sd_bus_request_name.xml b/man/sd_bus_request_name.xml index 7fae7becf4..c84b0b62fa 100644 --- a/man/sd_bus_request_name.xml +++ b/man/sd_bus_request_name.xml @@ -87,7 +87,7 @@ <varname>SD_BUS_NAME_REPLACE_EXISTING</varname> flag set. If <varname>SD_BUS_NAME_ALLOW_REPLACEMENT</varname> - is not set on the original request + is not set on the original request, such a request by other peers will be denied.</para></listitem> </varlistentry> @@ -125,10 +125,10 @@ errno-style error code.</para> <para>If <varname>SD_BUS_NAME_QUEUE</varname> is - specified <function>sd_bus_request_name()</function> + specified, <function>sd_bus_request_name()</function> will return 0 when the name is already taken by another peer and the client has been added to the - queue for the name. In that case the caller can + queue for the name. In that case, the caller can subscribe to <literal>NameOwnerChanged</literal> signals to be notified when the name is successfully acquired. <function>sd_bus_request_name()</function> diff --git a/man/sd_get_seats.xml b/man/sd_get_seats.xml index 1e55af3bdf..f0e7655d4c 100644 --- a/man/sd_get_seats.xml +++ b/man/sd_get_seats.xml @@ -107,7 +107,7 @@ <refsect1> <title>Return Value</title> - <para>On success <function>sd_get_seats()</function>, + <para>On success, <function>sd_get_seats()</function>, <function>sd_get_sessions()</function>, <function>sd_get_uids()</function> and <function>sd_get_machine_names()</function> return the diff --git a/man/sd_is_fifo.xml b/man/sd_is_fifo.xml index 5e79453cec..4bb2236fce 100644 --- a/man/sd_is_fifo.xml +++ b/man/sd_is_fifo.xml @@ -214,7 +214,7 @@ file. Alternatively, applications consuming these APIs may copy the implementation into their source tree. For more details about the reference - implementation see + implementation, see <citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para> <para>These functions continue to work as described, diff --git a/man/sd_listen_fds.xml b/man/sd_listen_fds.xml index aaabdbf3e8..6a9e082180 100644 --- a/man/sd_listen_fds.xml +++ b/man/sd_listen_fds.xml @@ -155,7 +155,7 @@ file. Alternatively, applications consuming these APIs may copy the implementation into their source tree. For more details about the reference - implementation see + implementation, see <citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para> <para>If the reference implementation is used as diff --git a/man/sd_login_monitor_new.xml b/man/sd_login_monitor_new.xml index f439d3e7b5..14ff241d82 100644 --- a/man/sd_login_monitor_new.xml +++ b/man/sd_login_monitor_new.xml @@ -198,13 +198,13 @@ else { <refsect1> <title>Return Value</title> - <para>On success + <para>On success, <function>sd_login_monitor_new()</function>, <function>sd_login_monitor_flush()</function> and <function>sd_login_monitor_get_timeout()</function> - return 0 or a positive integer. On success + return 0 or a positive integer. On success, <function>sd_login_monitor_get_fd()</function> returns - a Unix file descriptor. On success + a Unix file descriptor. On success, <function>sd_login_monitor_get_events()</function> returns a combination of <constant>POLLIN</constant>, <constant>POLLOUT</constant> and suchlike. On failure, diff --git a/man/sd_notify.xml b/man/sd_notify.xml index cd4a437f3f..d21820f67b 100644 --- a/man/sd_notify.xml +++ b/man/sd_notify.xml @@ -245,7 +245,7 @@ <constant>libsystemd-daemon</constant> <citerefentry><refentrytitle>pkg-config</refentrytitle><manvolnum>1</manvolnum></citerefentry> file. Alternatively, applications consuming these APIs may copy the implementation into their source tree. For - more details about the reference implementation see + more details about the reference implementation, see <citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para> <para>If the reference implementation is used as diff --git a/man/sd_readahead.xml b/man/sd_readahead.xml index bb01bcfd89..98272997cb 100644 --- a/man/sd_readahead.xml +++ b/man/sd_readahead.xml @@ -139,7 +139,7 @@ <filename>sd-readahead.h</filename> files. It is recommended that applications consuming this API copy the implementation into their source tree. For more - details about the reference implementation see + details about the reference implementation, see <citerefentry><refentrytitle>sd-readahead</refentrytitle><manvolnum>3</manvolnum></citerefentry></para> <para>If -DDISABLE_SYSTEMD is set during compilation, diff --git a/man/sd_seat_get_active.xml b/man/sd_seat_get_active.xml index 23d582da92..c64ba13c3a 100644 --- a/man/sd_seat_get_active.xml +++ b/man/sd_seat_get_active.xml @@ -143,9 +143,9 @@ <refsect1> <title>Return Value</title> - <para> On success + <para> On success, <function>sd_seat_get_active()</function> - returns 0 or a positive integer. On success + returns 0 or a positive integer. On success, <function>sd_seat_get_sessions()</function> returns the number of entries in the session identifier array. If the test succeeds, diff --git a/man/sd_session_is_active.xml b/man/sd_session_is_active.xml index d1f1a349d9..bff6b04eab 100644 --- a/man/sd_session_is_active.xml +++ b/man/sd_session_is_active.xml @@ -270,7 +270,7 @@ <para>If the test succeeds, <function>sd_session_is_active()</function> and <function>sd_session_is_remote()</function> return a - positive integer, if it fails 0. On success + positive integer; if it fails, 0. On success, <function>sd_session_get_state()</function>, <function>sd_session_get_uid()</function>, <function>sd_session_get_seat()</function>, diff --git a/man/sd_uid_get_state.xml b/man/sd_uid_get_state.xml index 0faa7651e5..30b254c805 100644 --- a/man/sd_uid_get_state.xml +++ b/man/sd_uid_get_state.xml @@ -152,11 +152,11 @@ <refsect1> <title>Return Value</title> - <para>On success + <para>On success, <function>sd_uid_get_state()</function> returns 0 or a positive integer. If the test succeeds, <function>sd_uid_is_on_seat()</function> returns a - positive integer, if it fails + positive integer; if it fails, 0. <function>sd_uid_get_sessions()</function> and <function>sd_uid_get_seats()</function> return the number of entries in the returned arrays. On failure, diff --git a/man/sd_watchdog_enabled.xml b/man/sd_watchdog_enabled.xml index 5b0d7e21cb..cad92df7af 100644 --- a/man/sd_watchdog_enabled.xml +++ b/man/sd_watchdog_enabled.xml @@ -80,7 +80,7 @@ inherited by child processes.</para> <para>If the <parameter>usec</parameter> parameter is - non-NULL <function>sd_watchdog_enabled()</function> + non-NULL, <function>sd_watchdog_enabled()</function> will return the timeout in µs for the watchdog logic. The service manager will usually terminate a service when it did not get a notification message @@ -94,7 +94,7 @@ <literal>WATCHDOG=1</literal>.</para> <para>To enable service supervision with the watchdog - logic use <varname>WatchdogSec=</varname> in service + logic, use <varname>WatchdogSec=</varname> in service files. See <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details.</para> @@ -107,7 +107,7 @@ errno-style error code. If the service manager expects watchdog keep-alive notification messages to be sent, > 0 is returned, otherwise 0 is returned. Only if - the return value is > 0 the + the return value is > 0, the <parameter>usec</parameter> parameter is valid after the call.</para> </refsect1> @@ -129,10 +129,10 @@ variable. The call will ignore these variables if <varname>$WATCHDOG_PID</varname> does containe the PID of the current process, under the assumption that in - that case the variables were set for a different + that case, the variables were set for a different process further up the process tree.</para> - <para>For details about the algorithm check the + <para>For details about the algorithm, check the liberally licensed reference implementation sources: <ulink url="http://cgit.freedesktop.org/systemd/systemd/plain/src/libsystemd-daemon/sd-daemon.c"/> and <ulink @@ -148,7 +148,7 @@ file. Alternatively, applications consuming these APIs may copy the implementation into their source tree. For more details about the reference - implementation see + implementation, see <citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para> <para>If the reference implementation is used as diff --git a/man/shutdown.xml b/man/shutdown.xml index 795fb66328..27e7e87b6c 100644 --- a/man/shutdown.xml +++ b/man/shutdown.xml @@ -164,7 +164,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/systemctl.xml b/man/systemctl.xml index 6f51135c86..7c9ffc81a3 100644 --- a/man/systemctl.xml +++ b/man/systemctl.xml @@ -238,7 +238,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>. applications.</para> <para><literal>ignore-requirements</literal> is similar to - <literal>ignore-dependencies</literal> but only causes the + <literal>ignore-dependencies</literal>, but only causes the requirement dependencies to be ignored, the ordering dependencies will still be honoured.</para> </listitem> @@ -1383,7 +1383,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service <refsect2> <title>Parameter Syntax</title> - <para>For unit commands the specified + <para>For unit commands, the specified <replaceable>NAME</replaceable> should be the full name of the unit, or an abbreviated name which is automatically extended with the <literal>.service</literal> suffix. @@ -1395,7 +1395,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service <programlisting># systemctl status dev-sda.device # systemctl status home.mount</programlisting></para> - <para>For unit file commands the + <para>For unit file commands, the specified <replaceable>NAME</replaceable> should be the full name of the unit file, or the absolute path to the unit file. <programlisting># systemctl link /path/to/foo.service</programlisting> diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml index 1898ca6fb1..cbf59e0a1a 100644 --- a/man/systemd-analyze.xml +++ b/man/systemd-analyze.xml @@ -300,7 +300,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/systemd-ask-password.xml b/man/systemd-ask-password.xml index 8af328dcfa..79902cbd9a 100644 --- a/man/systemd-ask-password.xml +++ b/man/systemd-ask-password.xml @@ -167,7 +167,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/systemd-cat.xml b/man/systemd-cat.xml index ffb1dfd50b..ba7a2cf0c7 100644 --- a/man/systemd-cat.xml +++ b/man/systemd-cat.xml @@ -158,7 +158,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/systemd-cgls.xml b/man/systemd-cgls.xml index d4520e64d7..955e0da37c 100644 --- a/man/systemd-cgls.xml +++ b/man/systemd-cgls.xml @@ -145,7 +145,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/systemd-cgtop.xml b/man/systemd-cgtop.xml index 01a0ae2163..38bddf183c 100644 --- a/man/systemd-cgtop.xml +++ b/man/systemd-cgtop.xml @@ -264,7 +264,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/systemd-coredumpctl.xml b/man/systemd-coredumpctl.xml index 9ccb67d12d..67f75d1c53 100644 --- a/man/systemd-coredumpctl.xml +++ b/man/systemd-coredumpctl.xml @@ -200,7 +200,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise. Not finding any matching coredumps is treated as failure. </para> diff --git a/man/systemd-delta.xml b/man/systemd-delta.xml index 4d3ab78040..ebaa3492f4 100644 --- a/man/systemd-delta.xml +++ b/man/systemd-delta.xml @@ -223,7 +223,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/systemd-machine-id-setup.xml b/man/systemd-machine-id-setup.xml index bc38d551ca..7b3aa7e9a0 100644 --- a/man/systemd-machine-id-setup.xml +++ b/man/systemd-machine-id-setup.xml @@ -116,7 +116,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/systemd-notify.xml b/man/systemd-notify.xml index a76934649a..e14977d054 100644 --- a/man/systemd-notify.xml +++ b/man/systemd-notify.xml @@ -172,7 +172,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/systemd-tmpfiles.xml b/man/systemd-tmpfiles.xml index 9b8932c635..3d11c491d4 100644 --- a/man/systemd-tmpfiles.xml +++ b/man/systemd-tmpfiles.xml @@ -183,7 +183,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/systemd-tty-ask-password-agent.xml b/man/systemd-tty-ask-password-agent.xml index 31a18ba4b0..cb5fb43d9c 100644 --- a/man/systemd-tty-ask-password-agent.xml +++ b/man/systemd-tty-ask-password-agent.xml @@ -148,7 +148,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/systemd.device.xml b/man/systemd.device.xml index 1bbd32248f..fa7074aaf1 100644 --- a/man/systemd.device.xml +++ b/man/systemd.device.xml @@ -75,7 +75,7 @@ udev tag (by default all block and network devices, and a few others). This may be used to define dependencies between devices and other units. To tag a - udev device use <literal>TAG+="systemd"</literal> in + udev device, use <literal>TAG+="systemd"</literal> in the udev rules file, see <citerefentry><refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum></citerefentry> for details.</para> diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index 207592dda7..2778497647 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -847,7 +847,7 @@ processes and mounts private <filename>/tmp</filename> and <filename>/var/tmp</filename> - directories inside it, that are not + directories inside it that are not shared by processes outside of the namespace. This is useful to secure access to temporary files of the diff --git a/man/systemd.mount.xml b/man/systemd.mount.xml index bd50f352e7..b181949b13 100644 --- a/man/systemd.mount.xml +++ b/man/systemd.mount.xml @@ -94,7 +94,7 @@ in a unit file <filename>home-lennart.mount</filename>. For details about the escaping logic used to convert a file system - path to a unit name see + path to a unit name, see <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> <para>Optionally, a mount unit may be accompanied by diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 94e72df9b4..8e6c20550d 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -441,7 +441,7 @@ <literal>one</literal> and <literal>two two</literal>, respectively. Since two commands are - specified + specified, <varname>Type=oneshot</varname> must be used.</para> diff --git a/man/systemd.special.xml b/man/systemd.special.xml index 863a029fe3..76bb5cdcf3 100644 --- a/man/systemd.special.xml +++ b/man/systemd.special.xml @@ -996,7 +996,7 @@ <filename>smartcard.target</filename>, <filename>sound.target</filename>.</para> - <para>In addition the following special unit is + <para>In addition, the following special unit is understood only when systemd runs as service instance:</para> <variablelist> diff --git a/man/systemd.swap.xml b/man/systemd.swap.xml index 0411232853..492309e536 100644 --- a/man/systemd.swap.xml +++ b/man/systemd.swap.xml @@ -85,7 +85,7 @@ <filename noindex='true'>/dev/sda5</filename> must be configured in a unit file <filename>dev-sda5.swap</filename>. For details about the escaping logic used to convert a - file system path to a unit name see + file system path to a unit name, see <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> <para>All swap units automatically get the appropriate diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml index 484287ccf6..7143f9f931 100644 --- a/man/systemd.timer.xml +++ b/man/systemd.timer.xml @@ -141,7 +141,7 @@ also include time units. Example: "OnBootSec=5h 30min" means 5 hours and 30 minutes after boot-up. For details - about the syntax of time spans see + about the syntax of time spans, see <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> <para>If a timer configured with @@ -182,7 +182,7 @@ event expressions. See <citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry> for more information on the syntax of - calendar event expressions. Otherwise + calendar event expressions. Otherwise, the semantics are similar to <varname>OnActiveSec=</varname> and related settings.</para> @@ -211,7 +211,7 @@ <varname>OnUnitInactiveSec=</varname> and ending the time configured with <varname>AccuracySec=</varname> - later. Within this time window the + later. Within this time window, the expiry time will be placed at a host-specific, randomized but stable position, that is synchronized between @@ -220,7 +220,7 @@ in networked installations, as well as optimizing power consumption to suppress unnecessary CPU wake-ups. To - get best accuracy set this option to + get best accuracy, set this option to 1us. Note that the timer is still subject to the timer slack configured via @@ -229,7 +229,7 @@ setting. See <citerefentry><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry> for details. To optimize power - consumption make sure to set this + consumption, make sure to set this value as high as possible and as low as necessary.</para></listitem> </varlistentry> diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 54d5590c81..0244570361 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -403,7 +403,7 @@ what the unit's purpose is, followed by how it is configured, followed by any other related documentation. This - option may be specified more than once + option may be specified more than once, in which case the specified list of URIs is merged. If the empty string is assigned to this option, the list is @@ -492,7 +492,7 @@ <varname>Requires=</varname> and <varname>RequiresOverridable=</varname>, respectively. However, if the units - listed here are not started already + listed here are not started already, they will not be started and the transaction will fail immediately. </para></listitem> @@ -506,7 +506,7 @@ listed in this option will be started if the configuring unit is. However, if the listed units fail to start - or cannot be added to the transaction + or cannot be added to the transaction, this has no impact on the validity of the transaction as a whole. This is the recommended way to hook start-up @@ -519,7 +519,7 @@ symlinks to a <filename>.wants/</filename> directory accompanying the unit file. For - details see above.</para></listitem> + details, see above.</para></listitem> </varlistentry> <varlistentry> @@ -528,7 +528,7 @@ <listitem><para>Configures requirement dependencies, very similar in style to <varname>Requires=</varname>, however - in addition to this behavior it also + in addition to this behavior, it also declares that this unit is stopped when any of the units listed suddenly disappears. Units can suddenly, @@ -577,9 +577,9 @@ be modified to be fixed (in case one or both jobs are not a required part of the transaction). In the latter - case the job that is not the required + case, the job that is not the required will be removed, or in case both are - not required the unit that conflicts + not required, the unit that conflicts will be started and the unit that is conflicted is stopped.</para></listitem> @@ -606,7 +606,7 @@ a common pattern to include a unit name in both the <varname>After=</varname> and - <varname>Requires=</varname> option in + <varname>Requires=</varname> option, in which case the unit listed will be started before the unit that is configured with these options. This @@ -686,13 +686,13 @@ directives (see <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details). If a unit that has this - setting set is started its processes + setting set is started, its processes will see the same <filename>/tmp</filename>, <filename>/tmp/var</filename> and network namespace as one listed unit that is started. If multiple listed - units are already started it is not + units are already started, it is not defined which namespace is joined. Note that this setting only has an effect if @@ -1270,7 +1270,7 @@ <row> <entry><literal>%p</literal></entry> <entry>Prefix name</entry> - <entry>For instantiated units this refers to the string before the <literal>@</literal> character of the unit name. For non-instantiated units this refers to the name of the unit with the type suffix removed.</entry> + <entry>For instantiated units, this refers to the string before the <literal>@</literal> character of the unit name. For non-instantiated units, this refers to the name of the unit with the type suffix removed.</entry> </row> <row> <entry><literal>%P</literal></entry> @@ -1325,12 +1325,12 @@ <row> <entry><literal>%h</literal></entry> <entry>User home directory</entry> - <entry>This is the home directory of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal> this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry> + <entry>This is the home directory of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal>, this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry> </row> <row> <entry><literal>%s</literal></entry> <entry>User shell</entry> - <entry>This is the shell of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal> this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry> + <entry>This is the shell of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal>, this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry> </row> <row> <entry><literal>%m</literal></entry> diff --git a/man/systemd.xml b/man/systemd.xml index 10ce375dae..acba820fdf 100644 --- a/man/systemd.xml +++ b/man/systemd.xml @@ -480,7 +480,7 @@ <filename>/proc</filename>.</para> <para>For more information about the concepts and - ideas behind systemd please refer to the <ulink + ideas behind systemd, please refer to the <ulink url="http://0pointer.de/blog/projects/systemd.html">Original Design Document</ulink>.</para> diff --git a/man/telinit.xml b/man/telinit.xml index bb8093914a..b20a60a4ca 100644 --- a/man/telinit.xml +++ b/man/telinit.xml @@ -171,7 +171,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> diff --git a/man/timedatectl.xml b/man/timedatectl.xml index afcb716e4e..beda304854 100644 --- a/man/timedatectl.xml +++ b/man/timedatectl.xml @@ -223,7 +223,7 @@ <refsect1> <title>Exit status</title> - <para>On success 0 is returned, a non-zero failure + <para>On success, 0 is returned, a non-zero failure code otherwise.</para> </refsect1> |