man: use unicode ellipsis in more places

As requested in
https://github.com/systemd/systemd/pull/4864#pullrequestreview-12372557.

docbook will substitute triple dots for the ellipsis in man output, so this has
no effect on the troff output, only on HTML, making it infinitesimally nicer.

In some places we show output from programs, which use dots, and those places
should not be changed. In some tables, the alignment would change if dots were
changed to the ellipsis which is only one character. Since docbook replaces the
ellipsis automatically, we should leave those be. This patch changes all other
places.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2016-12-11 17:01:07 -05:00
parent 15ffcc3456
commit 1eecafb8c1
29 changed files with 135 additions and 135 deletions

View File

@ -412,7 +412,7 @@
<term><option>--quiet</option></term>
<listitem><para>Suppresses all info messages
(i.e. "-- Logs begin at ...", "-- Reboot --"),
(i.e. "-- Logs begin at ", "-- Reboot --"),
any warning messages regarding
inaccessible system journals when run as a normal
user.</para></listitem>
@ -573,7 +573,7 @@
<listitem><para>The cursor is shown after the last entry after
two dashes:</para>
<programlisting>-- cursor: s=0639...</programlisting>
<programlisting>-- cursor: s=0639</programlisting>
<para>The format of the cursor is private
and subject to change.</para></listitem>
</varlistentry>
@ -731,7 +731,7 @@
<varlistentry>
<term><option>--list-catalog
<optional><replaceable>128-bit-ID...</replaceable></optional>
<optional><replaceable>128-bit-ID</replaceable></optional>
</option></term>
<listitem><para>List the contents of the message catalog as a
@ -745,7 +745,7 @@
<varlistentry>
<term><option>--dump-catalog
<optional><replaceable>128-bit-ID...</replaceable></optional>
<optional><replaceable>128-bit-ID</replaceable></optional>
</option></term>
<listitem><para>Show the contents of the message catalog, with

View File

@ -227,7 +227,7 @@
rotated journal files are kept as history.</para>
<para>Specify values in bytes or use K, M, G, T, P, E as
units for the specified sizes (equal to 1024, 1024², ... bytes).
units for the specified sizes (equal to 1024, 1024², bytes).
Note that size limits are enforced synchronously when journal
files are extended, and no explicit rotation step triggered by
time is needed.</para>

View File

@ -127,7 +127,7 @@
</varlistentry>
<varlistentry>
<term><command>set-locale LOCALE...</command></term>
<term><command>set-locale LOCALE</command></term>
<listitem><para>Set the system locale. This takes one or more
assignments such as "LANG=de_DE.utf8",

View File

@ -191,7 +191,7 @@
</varlistentry>
<varlistentry>
<term><command>session-status</command> <optional><replaceable>ID</replaceable>...</optional></term>
<term><command>session-status</command> <optional><replaceable>ID</replaceable></optional></term>
<listitem><para>Show terse runtime status information about
one or more sessions, followed by the most recent log data
@ -204,7 +204,7 @@
</varlistentry>
<varlistentry>
<term><command>show-session</command> <optional><replaceable>ID</replaceable>...</optional></term>
<term><command>show-session</command> <optional><replaceable>ID</replaceable></optional></term>
<listitem><para>Show properties of one or more sessions or the
manager itself. If no argument is specified, properties of the
@ -229,8 +229,8 @@
</varlistentry>
<varlistentry>
<term><command>lock-session</command> <optional><replaceable>ID</replaceable>...</optional></term>
<term><command>unlock-session</command> <optional><replaceable>ID</replaceable>...</optional></term>
<term><command>lock-session</command> <optional><replaceable>ID</replaceable></optional></term>
<term><command>unlock-session</command> <optional><replaceable>ID</replaceable></optional></term>
<listitem><para>Activates/deactivates the screen lock on one
or more sessions, if the session supports it. Takes one or
@ -248,7 +248,7 @@
</varlistentry>
<varlistentry>
<term><command>terminate-session</command> <replaceable>ID</replaceable>...</term>
<term><command>terminate-session</command> <replaceable>ID</replaceable></term>
<listitem><para>Terminates a session. This kills all processes
of the session and deallocates all resources attached to the
@ -256,7 +256,7 @@
</varlistentry>
<varlistentry>
<term><command>kill-session</command> <replaceable>ID</replaceable>...</term>
<term><command>kill-session</command> <replaceable>ID</replaceable></term>
<listitem><para>Send a signal to one or more processes of the
session. Use <option>--kill-who=</option> to select which
@ -274,7 +274,7 @@
</varlistentry>
<varlistentry>
<term><command>user-status</command> <optional><replaceable>USER</replaceable>...</optional></term>
<term><command>user-status</command> <optional><replaceable>USER</replaceable></optional></term>
<listitem><para>Show terse runtime status information about
one or more logged in users, followed by the most recent log
@ -288,7 +288,7 @@
</varlistentry>
<varlistentry>
<term><command>show-user</command> <optional><replaceable>USER</replaceable>...</optional></term>
<term><command>show-user</command> <optional><replaceable>USER</replaceable></optional></term>
<listitem><para>Show properties of one or more users or the
manager itself. If no argument is specified, properties of the
@ -303,8 +303,8 @@
</varlistentry>
<varlistentry>
<term><command>enable-linger</command> <optional><replaceable>USER</replaceable>...</optional></term>
<term><command>disable-linger</command> <optional><replaceable>USER</replaceable>...</optional></term>
<term><command>enable-linger</command> <optional><replaceable>USER</replaceable></optional></term>
<term><command>disable-linger</command> <optional><replaceable>USER</replaceable></optional></term>
<listitem><para>Enable/disable user lingering for one or more
users. If enabled for a specific user, a user manager is
@ -320,7 +320,7 @@
</varlistentry>
<varlistentry>
<term><command>terminate-user</command> <replaceable>USER</replaceable>...</term>
<term><command>terminate-user</command> <replaceable>USER</replaceable></term>
<listitem><para>Terminates all sessions of a user. This kills
all processes of all sessions of the user and deallocates all
@ -328,7 +328,7 @@
</varlistentry>
<varlistentry>
<term><command>kill-user</command> <replaceable>USER</replaceable>...</term>
<term><command>kill-user</command> <replaceable>USER</replaceable></term>
<listitem><para>Send a signal to all processes of a user. Use
<option>--signal=</option> to select the signal to send.
@ -345,7 +345,7 @@
</varlistentry>
<varlistentry>
<term><command>seat-status</command> <optional><replaceable>NAME</replaceable>...</optional></term>
<term><command>seat-status</command> <optional><replaceable>NAME</replaceable></optional></term>
<listitem><para>Show terse runtime status information about
one or more seats. Takes one or more seat names as parameters.
@ -357,7 +357,7 @@
</varlistentry>
<varlistentry>
<term><command>show-seat</command> <optional><replaceable>NAME</replaceable>...</optional></term>
<term><command>show-seat</command> <optional><replaceable>NAME</replaceable></optional></term>
<listitem><para>Show properties of one or more seats or the
manager itself. If no argument is specified, properties of the
@ -372,7 +372,7 @@
</varlistentry>
<varlistentry>
<term><command>attach</command> <replaceable>NAME</replaceable> <replaceable>DEVICE</replaceable>...</term>
<term><command>attach</command> <replaceable>NAME</replaceable> <replaceable>DEVICE</replaceable></term>
<listitem><para>Persistently attach one or more devices to a
seat. The devices should be specified via device paths in the
@ -396,7 +396,7 @@
</varlistentry>
<varlistentry>
<term><command>terminate-seat</command> <replaceable>NAME</replaceable>...</term>
<term><command>terminate-seat</command> <replaceable>NAME</replaceable></term>
<listitem><para>Terminates all sessions on a seat. This kills
all processes of all sessions on the seat and deallocates all
@ -426,9 +426,9 @@ fatima (1005)
Sessions: 5 *3
Unit: user-1005.slice
├─user@1005.service
...
├─session-3.scope
...
└─session-5.scope
├─3473 login -- fatima
└─3515 -zsh

View File

@ -327,7 +327,7 @@
</varlistentry>
<varlistentry>
<term><command>status</command> <replaceable>NAME</replaceable>...</term>
<term><command>status</command> <replaceable>NAME</replaceable></term>
<listitem><para>Show runtime status information about
one or more virtual machines and containers, followed by the
@ -341,7 +341,7 @@
</varlistentry>
<varlistentry>
<term><command>show</command> [<replaceable>NAME</replaceable>...]</term>
<term><command>show</command> [<replaceable>NAME</replaceable>]</term>
<listitem><para>Show properties of one or more registered virtual machines or containers or the manager
itself. If no argument is specified, properties of the manager will be shown. If a NAME is specified,
@ -353,7 +353,7 @@
</varlistentry>
<varlistentry>
<term><command>start</command> <replaceable>NAME</replaceable>...</term>
<term><command>start</command> <replaceable>NAME</replaceable></term>
<listitem><para>Start a container as a system service, using
<citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
@ -410,7 +410,7 @@
</varlistentry>
<varlistentry>
<term><command>shell</command> [[<replaceable>NAME</replaceable>@]<replaceable>NAME</replaceable> [<replaceable>PATH</replaceable> [<replaceable>ARGUMENTS</replaceable>...]]] </term>
<term><command>shell</command> [[<replaceable>NAME</replaceable>@]<replaceable>NAME</replaceable> [<replaceable>PATH</replaceable> [<replaceable>ARGUMENTS</replaceable>]]] </term>
<listitem><para>Open an interactive shell session in a
container or on the local host. The first argument refers to
@ -449,8 +449,8 @@
</varlistentry>
<varlistentry>
<term><command>enable</command> <replaceable>NAME</replaceable>...</term>
<term><command>disable</command> <replaceable>NAME</replaceable>...</term>
<term><command>enable</command> <replaceable>NAME</replaceable></term>
<term><command>disable</command> <replaceable>NAME</replaceable></term>
<listitem><para>Enable or disable a container as a system
service to start at system boot, using
@ -463,7 +463,7 @@
</varlistentry>
<varlistentry>
<term><command>poweroff</command> <replaceable>NAME</replaceable>...</term>
<term><command>poweroff</command> <replaceable>NAME</replaceable></term>
<listitem><para>Power off one or more containers. This will
trigger a reboot by sending SIGRTMIN+4 to the container's init
@ -478,7 +478,7 @@
</varlistentry>
<varlistentry>
<term><command>reboot</command> <replaceable>NAME</replaceable>...</term>
<term><command>reboot</command> <replaceable>NAME</replaceable></term>
<listitem><para>Reboot one or more containers. This will
trigger a reboot by sending SIGINT to the container's init
@ -488,7 +488,7 @@
</varlistentry>
<varlistentry>
<term><command>terminate</command> <replaceable>NAME</replaceable>...</term>
<term><command>terminate</command> <replaceable>NAME</replaceable></term>
<listitem><para>Immediately terminates a virtual machine or
container, without cleanly shutting it down. This kills all
@ -499,7 +499,7 @@
</varlistentry>
<varlistentry>
<term><command>kill</command> <replaceable>NAME</replaceable>...</term>
<term><command>kill</command> <replaceable>NAME</replaceable></term>
<listitem><para>Send a signal to one or more processes of the
virtual machine or container. This means processes as seen by
@ -568,7 +568,7 @@
</varlistentry>
<varlistentry>
<term><command>image-status</command> [<replaceable>NAME</replaceable>...]</term>
<term><command>image-status</command> [<replaceable>NAME</replaceable>]</term>
<listitem><para>Show terse status information about one or
more container or VM images. This function is intended to
@ -578,7 +578,7 @@
</varlistentry>
<varlistentry>
<term><command>show-image</command> [<replaceable>NAME</replaceable>...]</term>
<term><command>show-image</command> [<replaceable>NAME</replaceable>]</term>
<listitem><para>Show properties of one or more registered
virtual machine or container images, or the manager itself. If
@ -630,7 +630,7 @@
</varlistentry>
<varlistentry>
<term><command>remove</command> <replaceable>NAME</replaceable>...</term>
<term><command>remove</command> <replaceable>NAME</replaceable></term>
<listitem><para>Removes one or more container or VM images.
The special image <literal>.host</literal>, which refers to
@ -849,7 +849,7 @@
</varlistentry>
<varlistentry>
<term><command>cancel-transfers</command> <replaceable>ID</replaceable>...</term>
<term><command>cancel-transfers</command> <replaceable>ID</replaceable></term>
<listitem><para>Aborts a download, import or export of the
container or VM image with the specified ID. To list ongoing

View File

@ -102,7 +102,7 @@
<varlistentry>
<term>
<command>list</command>
<optional><replaceable>LINK...</replaceable></optional>
<optional><replaceable>LINK</replaceable></optional>
</term>
<listitem>
@ -122,7 +122,7 @@
<varlistentry>
<term>
<command>status</command>
<optional><replaceable>LINK...</replaceable></optional>
<optional><replaceable>LINK</replaceable></optional>
</term>
<listitem>
@ -150,7 +150,7 @@
<varlistentry>
<term>
<command>lldp</command>
<optional><replaceable>LINK...</replaceable></optional>
<optional><replaceable>LINK</replaceable></optional>
</term>
<listitem>

View File

@ -68,7 +68,7 @@
<funcsynopsisinfo>typedef struct {
const char *name;
const char *message;
...
} sd_bus_error;</funcsynopsisinfo>
<para>
@ -95,7 +95,7 @@
<paramdef>sd_bus_error *<parameter>e</parameter></paramdef>
<paramdef>const char *<parameter>name</parameter></paramdef>
<paramdef>const char *<parameter>format</parameter></paramdef>
<paramdef>...</paramdef>
<paramdef></paramdef>
</funcprototype>
<funcprototype>
@ -116,7 +116,7 @@
<paramdef>sd_bus_error *<parameter>e</parameter></paramdef>
<paramdef>int <parameter>error</parameter></paramdef>
<paramdef>const char *<parameter>format</parameter></paramdef>
<paramdef>...</paramdef>
<paramdef></paramdef>
</funcprototype>
<funcprototype>

View File

@ -58,7 +58,7 @@
<funcsynopsisinfo>typedef struct {
const char *name;
int code;
...
} sd_bus_error_map;</funcsynopsisinfo>
</funcsynopsis>

View File

@ -58,7 +58,7 @@
<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>
</funcsynopsis>
</refsynopsisdiv>
@ -198,7 +198,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>

View File

@ -66,7 +66,7 @@
<funcdef>int <function>sd_bus_path_encode_many</function></funcdef>
<paramdef>char **<parameter>out</parameter></paramdef>
<paramdef>const char *<parameter>path_template</parameter></paramdef>
<paramdef>...</paramdef>
<paramdef></paramdef>
</funcprototype>
<funcprototype>
@ -80,7 +80,7 @@
<funcdef>int <function>sd_bus_path_decode_many</function></funcdef>
<paramdef>const char *<parameter>path</parameter></paramdef>
<paramdef>const char *<parameter>path_template</parameter></paramdef>
<paramdef>...</paramdef>
<paramdef></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>

View File

@ -118,10 +118,10 @@
<parameter>family</parameter> parameter is not
<constant>AF_UNSPEC</constant>, it is checked whether the socket
is of the specified family (<constant>AF_UNIX</constant>,
<constant>AF_INET</constant>, ...). If the <parameter>type</parameter>
<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
<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

View File

@ -190,7 +190,7 @@
message ID 03bb1dab98ab4ecfbf6fff2738bdd964 coming from any
service (this example lacks the necessary error checking):</para>
<programlisting>...
<programlisting>
int add_matches(sd_journal *j) {
sd_journal_add_match(j, "_SYSTEMD_UNIT=avahi-daemon.service", 0);
sd_journal_add_match(j, "PRIORITY=0", 0);

View File

@ -207,14 +207,14 @@
iterate through all fields of the current journal
entry:</para>
<programlisting>...
<programlisting>
int print_fields(sd_journal *j) {
const void *data;
size_t length;
SD_JOURNAL_FOREACH_DATA(j, data, length)
printf("%.*s\n", (int) length, data);
}
...</programlisting>
</programlisting>
</refsect1>

View File

@ -60,7 +60,7 @@
<funcdef>int <function>sd_journal_print</function></funcdef>
<paramdef>int <parameter>priority</parameter></paramdef>
<paramdef>const char *<parameter>format</parameter></paramdef>
<paramdef>...</paramdef>
<paramdef></paramdef>
</funcprototype>
<funcprototype>
@ -73,7 +73,7 @@
<funcprototype>
<funcdef>int <function>sd_journal_send</function></funcdef>
<paramdef>const char *<parameter>format</parameter></paramdef>
<paramdef>...</paramdef>
<paramdef></paramdef>
</funcprototype>
<funcprototype>

View File

@ -79,7 +79,7 @@
received, zero is returned. The first file descriptor may be found
at file descriptor number 3
(i.e. <constant>SD_LISTEN_FDS_START</constant>), the remaining
descriptors follow at 4, 5, 6, ..., if any.</para>
descriptors follow at 4, 5, 6, , if any.</para>
<para>If a daemon receives more than one file descriptor, they
will be passed in the same order as configured in the systemd

View File

@ -66,7 +66,7 @@
<funcdef>int <function>sd_notifyf</function></funcdef>
<paramdef>int <parameter>unset_environment</parameter></paramdef>
<paramdef>const char *<parameter>format</parameter></paramdef>
<paramdef>...</paramdef>
<paramdef></paramdef>
</funcprototype>
<funcprototype>
@ -81,7 +81,7 @@
<paramdef>pid_t <parameter>pid</parameter></paramdef>
<paramdef>int <parameter>unset_environment</parameter></paramdef>
<paramdef>const char *<parameter>format</parameter></paramdef>
<paramdef>...</paramdef>
<paramdef></paramdef>
</funcprototype>
<funcprototype>
@ -152,7 +152,7 @@
</varlistentry>
<varlistentry>
<term>STATUS=...</term>
<term>STATUS=</term>
<listitem><para>Passes a single-line UTF-8 status string back
to the service manager that describes the service state. This
@ -160,11 +160,11 @@
state feedback, fsck-like programs could pass completion
percentages and failing programs could pass a human-readable
error message. Example: <literal>STATUS=Completed 66% of file
system check...</literal></para></listitem>
system check</literal></para></listitem>
</varlistentry>
<varlistentry>
<term>ERRNO=...</term>
<term>ERRNO=</term>
<listitem><para>If a service fails, the errno-style error
code, formatted as string. Example: <literal>ERRNO=2</literal>
@ -172,7 +172,7 @@
</varlistentry>
<varlistentry>
<term>BUSERROR=...</term>
<term>BUSERROR=</term>
<listitem><para>If a service fails, the D-Bus error-style
error code. Example:
@ -180,7 +180,7 @@
</varlistentry>
<varlistentry>
<term>MAINPID=...</term>
<term>MAINPID=</term>
<listitem><para>The main process ID (PID) of the service, in
case the service manager did not fork off the process itself.
@ -227,7 +227,7 @@
</varlistentry>
<varlistentry>
<term>FDNAME=...</term>
<term>FDNAME=</term>
<listitem><para>When used in combination with
<varname>FDSTORE=1</varname>, specifies a name for the
@ -248,7 +248,7 @@
</varlistentry>
<varlistentry>
<term>WATCHDOG_USEC=...</term>
<term>WATCHDOG_USEC=</term>
<listitem><para>Reset <varname>watchdog_usec</varname> value during runtime.
Notice that this is not available when using <function>sd_event_set_watchdog()</function>
@ -362,7 +362,7 @@
initialization:</para>
<programlisting>sd_notifyf(0, "READY=1\n"
"STATUS=Processing requests...\n"
"STATUS=Processing requests\n"
"MAINPID=%lu",
(unsigned long) getpid());</programlisting>
</example>

View File

@ -664,7 +664,7 @@
<variablelist>
<varlistentry>
<term><command>list-units <optional><replaceable>PATTERN</replaceable>...</optional></command></term>
<term><command>list-units <optional><replaceable>PATTERN</replaceable></optional></command></term>
<listitem>
<para>List units that <command>systemd</command> currently has in memory. This includes units that are
@ -680,7 +680,7 @@
</varlistentry>
<varlistentry>
<term><command>list-sockets <optional><replaceable>PATTERN</replaceable>...</optional></command></term>
<term><command>list-sockets <optional><replaceable>PATTERN</replaceable></optional></command></term>
<listitem>
<para>List socket units currently in memory, ordered by listening address. If one or more
@ -689,7 +689,7 @@
<programlisting>
LISTEN UNIT ACTIVATES
/dev/initctl systemd-initctl.socket systemd-initctl.service
...
[::]:22 sshd.socket sshd.service
kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
@ -703,7 +703,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>list-timers <optional><replaceable>PATTERN</replaceable>...</optional></command></term>
<term><command>list-timers <optional><replaceable>PATTERN</replaceable></optional></command></term>
<listitem>
<para>List timer units currently in memory, ordered by the time they elapse next. If one or more
@ -715,7 +715,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>start <replaceable>PATTERN</replaceable>...</command></term>
<term><command>start <replaceable>PATTERN</replaceable></command></term>
<listitem>
<para>Start (activate) one or more units specified on the
@ -729,7 +729,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>stop <replaceable>PATTERN</replaceable>...</command></term>
<term><command>stop <replaceable>PATTERN</replaceable></command></term>
<listitem>
<para>Stop (deactivate) one or more units specified on the
@ -737,7 +737,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>reload <replaceable>PATTERN</replaceable>...</command></term>
<term><command>reload <replaceable>PATTERN</replaceable></command></term>
<listitem>
<para>Asks all units listed on the command line to reload
@ -757,7 +757,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>restart <replaceable>PATTERN</replaceable>...</command></term>
<term><command>restart <replaceable>PATTERN</replaceable></command></term>
<listitem>
<para>Restart one or more units specified on the command
@ -766,7 +766,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>try-restart <replaceable>PATTERN</replaceable>...</command></term>
<term><command>try-restart <replaceable>PATTERN</replaceable></command></term>
<listitem>
<para>Restart one or more units specified on the command
@ -777,7 +777,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>reload-or-restart <replaceable>PATTERN</replaceable>...</command></term>
<term><command>reload-or-restart <replaceable>PATTERN</replaceable></command></term>
<listitem>
<para>Reload one or more units if they support it. If not,
@ -786,7 +786,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>try-reload-or-restart <replaceable>PATTERN</replaceable>...</command></term>
<term><command>try-reload-or-restart <replaceable>PATTERN</replaceable></command></term>
<listitem>
<para>Reload one or more units if they support it. If not,
@ -818,7 +818,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>kill <replaceable>PATTERN</replaceable>...</command></term>
<term><command>kill <replaceable>PATTERN</replaceable></command></term>
<listitem>
<para>Send a signal to one or more processes of the
@ -828,7 +828,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>is-active <replaceable>PATTERN</replaceable>...</command></term>
<term><command>is-active <replaceable>PATTERN</replaceable></command></term>
<listitem>
<para>Check whether any of the specified units are active
@ -840,7 +840,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>is-failed <replaceable>PATTERN</replaceable>...</command></term>
<term><command>is-failed <replaceable>PATTERN</replaceable></command></term>
<listitem>
<para>Check whether any of the specified units are in a
@ -852,7 +852,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>status</command> <optional><replaceable>PATTERN</replaceable>...|<replaceable>PID</replaceable>...]</optional></term>
<term><command>status</command> <optional><replaceable>PATTERN</replaceable>…|<replaceable>PID</replaceable>]</optional></term>
<listitem>
<para>Show terse runtime status information about one or
@ -879,7 +879,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>show</command> <optional><replaceable>PATTERN</replaceable>...|<replaceable>JOB</replaceable>...</optional></term>
<term><command>show</command> <optional><replaceable>PATTERN</replaceable>…|<replaceable>JOB</replaceable></optional></term>
<listitem>
<para>Show properties of one or more units, jobs, or the
@ -896,7 +896,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>cat <replaceable>PATTERN</replaceable>...</command></term>
<term><command>cat <replaceable>PATTERN</replaceable></command></term>
<listitem>
<para>Show backing files of one or more units. Prints the
@ -910,7 +910,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>set-property <replaceable>NAME</replaceable> <replaceable>ASSIGNMENT</replaceable>...</command></term>
<term><command>set-property <replaceable>NAME</replaceable> <replaceable>ASSIGNMENT</replaceable></command></term>
<listitem>
<para>Set the specified unit properties at runtime where
@ -941,7 +941,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>help <replaceable>PATTERN</replaceable>...|<replaceable>PID</replaceable>...</command></term>
<term><command>help <replaceable>PATTERN</replaceable>…|<replaceable>PID</replaceable></command></term>
<listitem>
<para>Show manual pages for one or more units, if
@ -951,7 +951,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>reset-failed [<replaceable>PATTERN</replaceable>...]</command></term>
<term><command>reset-failed [<replaceable>PATTERN</replaceable>]</command></term>
<listitem>
<para>Reset the <literal>failed</literal> state of the
@ -999,7 +999,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
<variablelist>
<varlistentry>
<term><command>list-unit-files <optional><replaceable>PATTERN...</replaceable></optional></command></term>
<term><command>list-unit-files <optional><replaceable>PATTERN</replaceable></optional></command></term>
<listitem>
<para>List unit files installed on the system, in combination with their enablement state (as reported by
@ -1010,8 +1010,8 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>enable <replaceable>NAME</replaceable>...</command></term>
<term><command>enable <replaceable>PATH</replaceable>...</command></term>
<term><command>enable <replaceable>NAME</replaceable></command></term>
<term><command>enable <replaceable>PATH</replaceable></command></term>
<listitem>
<para>Enable one or more units or unit instances. This will create a set of symlinks, as encoded in the
@ -1061,7 +1061,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>disable <replaceable>NAME</replaceable>...</command></term>
<term><command>disable <replaceable>NAME</replaceable></command></term>
<listitem>
<para>Disables one or more units. This removes all symlinks to the unit files backing the specified units
@ -1093,7 +1093,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>reenable <replaceable>NAME</replaceable>...</command></term>
<term><command>reenable <replaceable>NAME</replaceable></command></term>
<listitem>
<para>Reenable one or more units, as specified on the command line. This is a combination of
@ -1104,7 +1104,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>preset <replaceable>NAME</replaceable>...</command></term>
<term><command>preset <replaceable>NAME</replaceable></command></term>
<listitem>
<para>Reset the enable/disable status one or more unit files, as specified on
@ -1142,7 +1142,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>is-enabled <replaceable>NAME</replaceable>...</command></term>
<term><command>is-enabled <replaceable>NAME</replaceable></command></term>
<listitem>
<para>Checks whether any of the specified unit files are
@ -1229,7 +1229,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>mask <replaceable>NAME</replaceable>...</command></term>
<term><command>mask <replaceable>NAME</replaceable></command></term>
<listitem>
<para>Mask one or more units, as specified on the command line. This will link these unit files to
@ -1243,7 +1243,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>unmask <replaceable>NAME</replaceable>...</command></term>
<term><command>unmask <replaceable>NAME</replaceable></command></term>
<listitem>
<para>Unmask one or more unit files, as specified on the command line. This will undo the effect of
@ -1253,7 +1253,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>link <replaceable>PATH</replaceable>...</command></term>
<term><command>link <replaceable>PATH</replaceable></command></term>
<listitem>
<para>Link a unit file that is not in the unit file search paths into the unit file search path. This
@ -1264,7 +1264,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>revert <replaceable>NAME</replaceable>...</command></term>
<term><command>revert <replaceable>NAME</replaceable></command></term>
<listitem>
<para>Revert one or more unit files to their vendor versions. This command removes drop-in configuration
@ -1287,9 +1287,9 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
<varlistentry>
<term><command>add-wants <replaceable>TARGET</replaceable>
<replaceable>NAME</replaceable>...</command></term>
<replaceable>NAME</replaceable></command></term>
<term><command>add-requires <replaceable>TARGET</replaceable>
<replaceable>NAME</replaceable>...</command></term>
<replaceable>NAME</replaceable></command></term>
<listitem>
<para>Adds <literal>Wants=</literal> or <literal>Requires=</literal>
@ -1305,7 +1305,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</varlistentry>
<varlistentry>
<term><command>edit <replaceable>NAME</replaceable>...</command></term>
<term><command>edit <replaceable>NAME</replaceable></command></term>
<listitem>
<para>Edit a drop-in snippet or a whole replacement file if
@ -1372,7 +1372,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
<variablelist>
<varlistentry>
<term><command>list-machines <optional><replaceable>PATTERN</replaceable>...</optional></command></term>
<term><command>list-machines <optional><replaceable>PATTERN</replaceable></optional></command></term>
<listitem>
<para>List the host and all running local containers with
@ -1390,7 +1390,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
<variablelist>
<varlistentry>
<term><command>list-jobs <optional><replaceable>PATTERN...</replaceable></optional></command></term>
<term><command>list-jobs <optional><replaceable>PATTERN</replaceable></optional></command></term>
<listitem>
<para>List jobs that are in progress. If one or more
@ -1403,7 +1403,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>cancel <replaceable>JOB</replaceable>...</command></term>
<term><command>cancel <replaceable>JOB</replaceable></command></term>
<listitem>
<para>Cancel one or more jobs specified on the command line
@ -1430,7 +1430,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>set-environment <replaceable>VARIABLE=VALUE</replaceable>...</command></term>
<term><command>set-environment <replaceable>VARIABLE=VALUE</replaceable></command></term>
<listitem>
<para>Set one or more systemd manager environment variables,
@ -1438,7 +1438,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
</listitem>
</varlistentry>
<varlistentry>
<term><command>unset-environment <replaceable>VARIABLE</replaceable>...</command></term>
<term><command>unset-environment <replaceable>VARIABLE</replaceable></command></term>
<listitem>
<para>Unset one or more systemd manager environment
@ -1451,7 +1451,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
<varlistentry>
<term>
<command>import-environment</command>
<optional><replaceable>VARIABLE...</replaceable></optional>
<optional><replaceable>VARIABLE</replaceable></optional>
</term>
<listitem>
@ -1759,7 +1759,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
<title>Parameter Syntax</title>
<para>Unit commands listed above take either a single unit name (designated as <replaceable>NAME</replaceable>),
or multiple unit specifications (designated as <replaceable>PATTERN</replaceable>...). In the first case, the
or multiple unit specifications (designated as <replaceable>PATTERN</replaceable>). In the first case, the
unit name with or without a suffix must be given. If the suffix is not specified (unit name is "abbreviated"),
systemctl will append a suitable suffix, <literal>.service</literal> by default, and a type-specific suffix in
case of commands which operate only on specific unit types. For example,

View File

@ -105,7 +105,7 @@
<command>systemd-analyze</command>
<arg choice="opt" rep="repeat">OPTIONS</arg>
<arg choice="plain">syscall-filter</arg>
<arg choice="opt"><replaceable>SET</replaceable>...</arg>
<arg choice="opt"><replaceable>SET</replaceable></arg>
</cmdsynopsis>
<cmdsynopsis>
<command>systemd-analyze</command>
@ -140,7 +140,7 @@
initialization of another service to complete.</para>
<para><command>systemd-analyze critical-chain
[<replaceable>UNIT...</replaceable>]</command> prints a tree of
[<replaceable>UNIT</replaceable>]</command> prints a tree of
the time-critical chain of units (for each of the specified
<replaceable>UNIT</replaceable>s or for the default target
otherwise). The time after the unit is active or started is
@ -187,7 +187,7 @@
<option>--log-target=</option>, described in
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>).</para>
<para><command>systemd-analyze syscall-filter <optional><replaceable>SET</replaceable>...</optional></command>
<para><command>systemd-analyze syscall-filter <optional><replaceable>SET</replaceable></optional></command>
will list system calls contained in the specified system call set <replaceable>SET</replaceable>,
or all known sets if no sets are specified. Argument <replaceable>SET</replaceable> must include
the <literal>@</literal> prefix.</para>

View File

@ -63,7 +63,7 @@
compare configuration files that override other configuration
files. Files in <filename>/etc</filename> have highest priority,
files in <filename>/run</filename> have the second highest
priority, ..., files in <filename>/lib</filename> have lowest
priority, , files in <filename>/lib</filename> have lowest
priority. Files in a directory with higher priority override files
with the same name in directories of lower priority. In addition,
certain configuration files can have <literal>.d</literal>
@ -82,7 +82,7 @@
suffix. Either is optional. The prefix must be one of the
directories containing configuration files
(<filename>/etc</filename>, <filename>/run</filename>,
<filename>/usr/lib</filename>, ...). If it is given, only
<filename>/usr/lib</filename>, ). If it is given, only
overriding files contained in this directory will be shown.
Otherwise, all overriding files will be shown. The suffix must be
a name of a subdirectory containing configuration files like

View File

@ -128,7 +128,7 @@
</varlistentry>
<varlistentry>
<term><uri>/entries[?option1&amp;option2=value...]</uri></term>
<term><uri>/entries[?option1&amp;option2=value]</uri></term>
<listitem><para>Retrieval of events in various formats.</para>
@ -157,7 +157,7 @@
"hostname" : "fedora",
"os_pretty_name" : "Fedora 19 (Rawhide)",
"virtualization" : "kvm",
...}</programlisting>
}</programlisting>
</para>
</listitem>
</varlistentry>

View File

@ -112,7 +112,7 @@
<listitem><para>Send a free-form status string for the daemon
to the init systemd. This option takes the status string as
argument. This is equivalent to <command>systemd-notify
STATUS=...</command>. For details about the semantics of this
STATUS=</command>. For details about the semantics of this
option see
<citerefentry><refentrytitle>sd_notify</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para></listitem>
</varlistentry>
@ -158,15 +158,15 @@
<programlisting>#!/bin/bash
mkfifo /tmp/waldo
systemd-notify --ready --status="Waiting for data..."
systemd-notify --ready --status="Waiting for data"
while : ; do
read a &lt; /tmp/waldo
systemd-notify --status="Processing $a"
# Do something with $a ...
# Do something with $a
systemd-notify --status="Waiting for data..."
systemd-notify --status="Waiting for data"
done</programlisting>
</example>
</refsect1>

View File

@ -120,7 +120,7 @@
originating from local, trusted sources is also reported authenticated, including resolution of the local host
name, the <literal>localhost</literal> host name or all data from <filename>/etc/hosts</filename>.</para>
<para>The <option>--type=</option> switch may be used to specify a DNS resource record type (A, AAAA, SOA, MX, ...) in
<para>The <option>--type=</option> switch may be used to specify a DNS resource record type (A, AAAA, SOA, MX, ) in
order to request a specific DNS resource record, instead of the address or reverse address lookups.
The special value <literal>help</literal> may be used to list known values.</para>
@ -356,7 +356,7 @@ _xmpp-server._tcp/gmail.com: alt1.xmpp-server.l.google.com:5269 [priority=20, we
173.194.210.125
alt4.xmpp-server.l.google.com:5269 [priority=20, weight=0]
173.194.65.125
...
</programlisting>
</example>
@ -367,7 +367,7 @@ _xmpp-server._tcp/gmail.com: alt1.xmpp-server.l.google.com:5269 [priority=20, we
d08ee310438ca124a6149ea5cc21b6313b390dce485576eff96f8722._openpgpkey.fedoraproject.org. IN OPENPGPKEY
mQINBFBHPMsBEACeInGYJCb+7TurKfb6wGyTottCDtiSJB310i37/6ZYoeIay/5soJjlMyf
MFQ9T2XNT/0LM6gTa0MpC1st9LnzYTMsT6tzRly1D1UbVI6xw0g0vE5y2Cjk3xUwAynCsSs
...
</programlisting>
</example>

View File

@ -136,7 +136,7 @@
</varlistentry>
<varlistentry>
<term><option>--fdname=</option><replaceable>NAME</replaceable><optional>:<replaceable>NAME</replaceable>...</optional></term>
<term><option>--fdname=</option><replaceable>NAME</replaceable><optional>:<replaceable>NAME</replaceable></optional></term>
<listitem><para>Specify names for the file descriptors passed. This is equivalent to setting
<varname>FileDescriptorName=</varname> in socket unit files, and enables use of

View File

@ -127,10 +127,10 @@ PrivateNetwork=yes]]></programlisting>
<example>
<title>nginx.conf</title>
<programlisting>
<![CDATA[[...]
<![CDATA[[]
server {
listen unix:/tmp/nginx.sock;
[...]]]>
[]]]>
</programlisting>
</example>
<example>
@ -169,10 +169,10 @@ PrivateNetwork=yes]]></programlisting>
</example>
<example>
<title>nginx.conf</title>
<programlisting><![CDATA[[...]
<programlisting><![CDATA[[]
server {
listen 8080;
[...]]]></programlisting>
[]]]></programlisting>
</example>
<example>
<title>Enabling the proxy</title>

View File

@ -919,8 +919,8 @@
as <literal>\;</literal>.</para>
<para>Each command line is split on whitespace, with the first item being the command to
execute, and the subsequent items being the arguments. Double quotes ("...") and single quotes
('...') may be used, in which case everything until the next matching quote becomes part of the
execute, and the subsequent items being the arguments. Double quotes ("") and single quotes
('') may be used, in which case everything until the next matching quote becomes part of the
same argument. Quotes themselves are removed. C-style escapes are also supported. The table
below contains the list of known escape patterns. Only escape patterns which match the syntax in
the table are allowed; other patterns may be added in the future and unknown patterns will

View File

@ -930,7 +930,7 @@ Description=Render the desktop icons with Nautilus
PartOf=graphical-session.target
[Service]
...
</programlisting>
</example>
</refsect2>

View File

@ -280,9 +280,9 @@
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
however some are created automatically from other configuration,
dynamically from system state or programmatically at runtime.
Units may be "active" (meaning started, bound, plugged in, ...,
Units may be "active" (meaning started, bound, plugged in, ,
depending on the unit type, see below), or "inactive" (meaning
stopped, unbound, unplugged, ...), as well as in the process of
stopped, unbound, unplugged, ), as well as in the process of
being activated or deactivated, i.e. between the two states (these
states are called "activating", "deactivating"). A special
"failed" state is available as well, which is very similar to

View File

@ -114,10 +114,10 @@
<listitem><para>Change the SysV runlevel. This is translated
into an activation request for
<filename>runlevel2.target</filename>,
<filename>runlevel3.target</filename>, ... and is equivalent
<filename>runlevel3.target</filename>, and is equivalent
to <command>systemctl isolate runlevel2.target</command>,
<command>systemctl isolate runlevel3.target</command>,
...</para></listitem>
</para></listitem>
</varlistentry>
<varlistentry>

View File

@ -232,7 +232,7 @@ Password: ********
Status: "Using Time Server 216.239.38.15:123 (time4.google.com)."
CGroup: /system.slice/systemd-timesyncd.service
└─595 /usr/lib/systemd/systemd-timesyncd
...</programlisting>
</programlisting>
</para>
</refsect1>