<term><option>--type=</option></term>
<listitem>
- <para>The argument should be a unit type name such as
- <option>service</option> and <option>socket</option>, or a
- unit load state such as <option>loaded</option> and
- <option>masked</option>.
+ <para>The argument should be a comma-separated list of unit
+ types such as <option>service</option> and
+ <option>socket</option>.
</para>
- <para>If the argument is a unit type, when listing units,
- limit display to certain unit types. If not specified units
+ <para>If one of the arguments is a unit type, when listing
+ units, limit display to certain unit types. Otherwise, units
of all types will be shown.</para>
- <para>If the argument is a unit load state, when listing
- units, limit display to certain unit types. If not specified
- units of in all load states will be shown.</para>
-
- <para>As a special case, if the argument is
+ <para>As a special case, if one of the arguments is
<option>help</option>, a list of allowed values will be
printed and the program will exit.</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>--state=</option></term>
+
+ <listitem>
+ <para>The argument should be a comma-separated list of unit LOAD
+ or SUB or ACTIVE states. When listing units, show only those
+ with specified LOAD or SUB or ACTIVE state.</para>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term><option>-p</option></term>
<term><option>--property=</option></term>
<listitem>
- <para>When showing unit/job/manager properties, limit
- display to certain properties as specified as argument. If
- not specified all set properties are shown. The argument
- should be a property name, such as
- <literal>MainPID</literal>. If specified more than once all
- properties with the specified names are
- shown.</para>
+ <para>When showing unit/job/manager properties with the
+ <command>show</command> command, limit display to certain
+ properties as specified as argument. If not specified, all
+ set properties are shown. The argument should be a
+ comma-separated list of property names, such as
+ <literal>MainPID</literal>. If specified more than once, all
+ properties with the specified names are shown.</para>
</listitem>
</varlistentry>
<term><option>--all</option></term>
<listitem>
- <para>When listing units, show all units, regardless of
- their state, including inactive units. When showing
+ <para>When listing units, show all loaded units, regardless
+ of their state, including inactive units. When showing
unit/job/manager properties, show all properties regardless
whether they are set or not.</para>
+ <para>To list all units installed on the system, use the
+ <command>list-unit-files</command> command instead.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--reverse</option></term>
+
+ <listitem>
+ <para>Show reverse dependencies between units with
+ <command>list-dependencies</command>, i.e. units with
+ dependencies of type <varname>Wants=</varname> or
+ <varname>Requires=</varname> on the given unit.
+ </para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--failed</option></term>
+ <term><option>--after</option></term>
+ <term><option>--before</option></term>
<listitem>
- <para>When listing units, show only failed units. Do not
- confuse with <option>--fail</option>.</para>
+ <para>Show which units are started after or before
+ with <command>list-dependencies</command>, respectively.
+ </para>
</listitem>
</varlistentry>
<varlistentry>
+ <term><option>-l</option></term>
<term><option>--full</option></term>
<listitem>
<listitem>
<para>If the requested operation conflicts with a pending
- unfinished job, fail the command. If this is not specified
+ unfinished job, fail the command. If this is not specified,
the requested operation will replace the pending job, if
necessary. Do not confuse with
<option>--failed</option>.</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>--show-types</option></term>
+
+ <listitem>
+ <para>When showing sockets, show the type of the socket.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--irreversible</option></term>
+
+ <listitem>
+ <para>Mark this transaction's jobs as irreversible. This prevents
+ future conflicting transactions from replacing these jobs.
+ The jobs can still be cancelled using the <command>cancel</command>
+ command.</para>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term><option>--ignore-dependencies</option></term>
<listitem>
- <para>When enqueuing a new job ignore all its dependencies
- and execute it immediately. If passed no required units of
+ <para>When enqueuing a new job, ignore all its dependencies
+ and execute it immediately. If passed, no required units of
the unit passed will be pulled in, and no ordering
dependencies will be honored. This is mostly a debugging and
rescue tool for the administrator and should not be used by
sleep state. Any user may take these locks and privileged
users may override these locks. If any locks are taken,
shutdown and sleep state requests will normally fail
- (regardless if privileged or not) and list of active locks
- is printed. However if <option>--ignore-inhibitors</option>
- is specified the locks are ignored and not printed, and the
+ (regardless if privileged or not) and a list of active locks
+ is printed. However, if <option>--ignore-inhibitors</option>
+ is specified, the locks are ignored and not printed, and the
operation attempted anyway, possibly requiring additional
privileges.</para>
</listitem>
<listitem>
<para>Do not synchronously wait for the requested operation
- to finish. If this is not specified the job will be
+ to finish. If this is not specified, the job will be
verified, enqueued and <command>systemctl</command> will
- wait until it is completed. By passing this argument it is
+ wait until it is completed. By passing this argument, it is
only verified and enqueued.</para>
</listitem>
</varlistentry>
<term><option>--no-wall</option></term>
<listitem>
- <para>Don't send wall message before halt, power-off,
+ <para>Do not send wall message before halt, power-off,
reboot.</para>
</listitem>
</varlistentry>
may require input of a password or passphrase string, for
example to unlock system hard disks or cryptographic
certificates. Unless this option is specified and the
- command is invoked from a terminal
+ command is invoked from a terminal,
<command>systemctl</command> will query the user on the
terminal for the necessary secrets. Use this option to
- switch this behavior off. In this case the password must be
+ switch this behavior off. In this case, the password must be
supplied by some other means (for example graphical password
agents) or the service might fail. This also disables
querying the user for authentication for privileged
processes to kill. Must be one of <option>main</option>,
<option>control</option> or <option>all</option> to select
whether to kill only the main process of the unit, the
- control process or all processes of the unit. If omitted
+ control process or all processes of the unit. If omitted,
defaults to <option>all</option>.</para>
</listitem>
<listitem>
<para>When used with <command>kill</command>, choose which
signal to send to selected processes. Must be one of the
- well known signal specifiers such as SIGTERM, SIGINT or
- SIGSTOP. If omitted defaults to
+ well known signal specifiers such as <constant>SIGTERM</constant>, <constant>SIGINT</constant> or
+ <constant>SIGSTOP</constant>. If omitted, defaults to
<option>SIGTERM</option>.</para>
</listitem>
</varlistentry>
<para>When used with <command>halt</command>,
<command>poweroff</command>, <command>reboot</command> or
- <command>kexec</command> execute the selected operation
+ <command>kexec</command>, execute the selected operation
without shutting down all units. However, all processes will
be killed forcibly and all file systems are unmounted or
remounted read-only. This is hence a drastic but relatively
<term><option>--runtime</option></term>
<listitem>
- <para>When used with
- <command>enable</command>/<command>disable</command>/<command>is-enabled</command>
+ <para>When used with <command>enable</command>,
+ <command>disable</command>, <command>is-enabled</command>
(and related commands), make changes only temporarily, so
- that they are dropped on the next reboot. This will have the
+ that they are lost on the next reboot. This will have the
effect that changes are not made in subdirectories of
<filename>/etc</filename> but in <filename>/run</filename>,
with identical immediate effects, however, since the latter
is lost on reboot, the changes are lost too.</para>
+
+ <para>Similar, when used with
+ <command>set-property</command>, make changes only
+ temporarily, so that they are lost on the next
+ reboot.</para>
</listitem>
</varlistentry>
<listitem>
<para>Execute operation remotely. Specify a hostname, or
- username and hostname separated by @, to connect to. This
+ username and hostname separated by <literal>@</literal>, to connect to. This
will use SSH to talk to the remote systemd
instance.</para>
</listitem>
<term><option>--lines=</option></term>
<listitem>
- <para>When used with <command>status</command> controls the
+ <para>When used with <command>status</command>, controls the
number of journal lines to show, counting from the most
recent ones. Takes a positive integer argument. Defaults to
10.</para>
<term><option>--output=</option></term>
<listitem>
- <para>When used with <command>status</command> controls the
+ <para>When used with <command>status</command>, controls the
formatting of the journal entries that are shown. For the
- available choices see
+ available choices, see
<citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
Defaults to <literal>short</literal>.</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>--plain</option></term>
+
+ <listitem>
+ <para>When used with <command>list-dependencies</command>,
+ the output is printed as a list instead of a tree.</para>
+ </listitem>
+ </varlistentry>
+
</variablelist>
</refsect1>
<para>This is the default command.</para>
</listitem>
</varlistentry>
+
+ <varlistentry>
+ <term><command>list-sockets</command></term>
+
+ <listitem>
+ <para>List socket units ordered by the listening address. Produces output
+ similar to
+ <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
+
+5 sockets listed.
+ </programlisting>
+ Note: because the addresses might contains spaces, this output
+ is not suitable for programmatic consumption.
+ </para>
+
+ <para>See also the options <option>--show-types</option>,
+ <option>--all</option>, and <option>--failed</option>.</para>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term><command>start <replaceable>NAME</replaceable>...</command></term>
for the example case of Apache, this will reload Apache's
<filename>httpd.conf</filename> in the web server, not the
<filename>apache.service</filename> systemd unit
- file. </para>
+ file.</para>
<para>This command should not be confused with the
<command>daemon-reload</command> or <command>load</command>
<listitem>
<para>Restart one or more units specified on the command
- line. If the units are not running yet they will be
+ line. If the units are not running yet, they will be
started.</para>
</listitem>
</varlistentry>
<listitem>
<para>Restart one or more units specified on the command
- line if the units are running. Do nothing if units are not
- running. Note that for compatibility with Red Hat init
- scripts <command>condrestart</command> is equivalent to this
+ line if the units are running. This does nothing if units are not
+ running. Note that, for compatibility with Red Hat init
+ scripts, <command>condrestart</command> is equivalent to this
command.</para>
</listitem>
</varlistentry>
<listitem>
<para>Reload one or more units if they support it. If not,
- restart them instead. If the units are not running yet they
+ restart them instead. If the units are not running yet, they
will be started.</para>
</listitem>
</varlistentry>
<listitem>
<para>Reload one or more units if they support it. If not,
- restart them instead. Do nothing if the units are not
- running. Note that for compatibility with SysV init scripts
+ restart them instead. This does nothing if the units are not
+ running. Note that, for compatibility with SysV init scripts,
<command>force-reload</command> is equivalent to this
command.</para>
</listitem>
<para>Check whether any of the specified units are active
(i.e. running). Returns an exit code 0 if at least one is
active, non-zero otherwise. Unless <option>--quiet</option>
- is specified this will also print the current unit state to
+ is specified, this will also print the current unit state to
STDOUT.</para>
</listitem>
</varlistentry>
<term><command>is-failed <replaceable>NAME</replaceable>...</command></term>
<listitem>
- <para>Check whether any of the specified units are failed.
- Returns an exit code 0 if at least one is failed, non-zero
- otherwise. Unless <option>--quiet</option> is specified this
+ <para>Check whether any of the specified units are in a "failed" state.
+ Returns an exit code 0 if at least one has failed, non-zero
+ otherwise. Unless <option>--quiet</option> is specified, this
will also print the current unit state to
STDOUT.</para>
</listitem>
more units, followed by most recent log data from the
journal. If no units are specified, show all units (subject
to limitations specified with <option>-t</option>). If a PID
- is passed show information about the unit the process
+ is passed, show information about the unit the process
belongs to.</para>
<para>This function is intended to generate human-readable
human-readable output.</para>
</listitem>
</varlistentry>
+
+ <varlistentry>
+ <term><command>set-property <replaceable>NAME</replaceable> <replaceable>ASSIGNMENT</replaceable>...</command></term>
+
+ <listitem>
+ <para>Set the specified unit properties at runtime where
+ this is supported. This allows changing configuration
+ parameter properties such as resource management controls at
+ runtime. Not all properties may be changed at runtime, but
+ many resource management settings (primarily those in
+ <citerefentry><refentrytitle>systemd.cgroup</refentrytitle><manvolnum>5</manvolnum></citerefentry>)
+ may. The changes are applied instantly, and stored on disk
+ for future boots, unless <option>--runtime</option> is
+ passed, in which case the settings only apply until the next
+ reboot. The syntax of the property assignment follows
+ closely the syntax of assignments in unit files.</para>
+
+ <para>Example: <command>systemctl set-property foobar.service CPUShares=777</command></para>
+
+ <para>Note that this command allows changing multiple
+ properties at the same time, which is preferable over
+ setting them individually. Like unit file configuration
+ settings, assigning the empty list to list parameters will
+ reset the list.</para>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term><command>help <replaceable>NAME</replaceable>...|<replaceable>PID</replaceable>...</command></term>
<listitem>
<para>Show manual pages for one or more units, if
- available. If a PID is passed the manual pages for the unit
- the process of the PID belongs to is
- shown.</para>
+ available. If a PID is given, the manual pages for the unit
+ the process belongs to are shown.</para>
</listitem>
</varlistentry>
+
<varlistentry>
<term><command>reset-failed [<replaceable>NAME</replaceable>...]</command></term>
<listitem>
<para>Reset the <literal>failed</literal> state of the
- specified units, or if no unit name is passed of all
+ specified units, or if no unit name is passed, reset the state of all
units. When a unit fails in some way (i.e. process exiting
with non-zero error code, terminating abnormally or timing
- out) it will automatically enter the
+ out), it will automatically enter the
<literal>failed</literal> state and its exit code and status
is recorded for introspection by the administrator until the
service is restarted or reset with this command.</para>
as specified on the command line. This will create a number
of symlinks as encoded in the <literal>[Install]</literal>
sections of the unit files. After the symlinks have been
- created the systemd configuration is reloaded (in a way that
+ created, the systemd configuration is reloaded (in a way that
is equivalent to <command>daemon-reload</command>) to ensure
the changes are taken into account immediately. Note that
- this does not have the effect that any of the units enabled
- are also started at the same time. If this is desired a
- separate <command>start</command> command must be invoked
- for the unit. Also note that in case of instance enablement,
- symlinks named same as instances are created in install
- location, however they all point to the same template unit
- file.</para>
+ this does <emphasis>not</emphasis> have the effect of also
+ starting any of the units being enabled. If this
+ is desired, a separate <command>start</command> command must
+ be invoked for the unit. Also note that in case of instance
+ enablement, symlinks named the same as instances are created in
+ the install location, however they all point to the same
+ template unit file.</para>
<para>This command will print the actions executed. This
output may be suppressed by passing <option>--quiet</option>.
symlinks for the units. While this command is the
recommended way to manipulate the unit configuration
directory, the administrator is free to make additional
- changes manually, by placing or removing symlinks in the
+ changes manually by placing or removing symlinks in the
directory. This is particularly useful to create
configurations that deviate from the suggested default
- installation. In this case the administrator must make sure
+ installation. In this case, the administrator must make sure
to invoke <command>daemon-reload</command> manually as
- necessary, to ensure his changes are taken into account.
+ necessary to ensure the changes are taken into account.
</para>
<para>Enabling units should not be confused with starting
<para>Depending on whether <option>--system</option>,
<option>--user</option> or <option>--global</option> is
- specified this enables the unit for the system, for the
+ specified, this enables the unit for the system, for the
calling user only or for all future logins of all
- users. Note that in the last case no systemd daemon
+ users. Note that in the last case, no systemd daemon
configuration is reloaded.</para>
</listitem>
</varlistentry>
<command>enable</command>. This call implicitly reloads the
systemd daemon configuration after completing the disabling
of the units. Note that this command does not implicitly
- stop the units that are being disabled. If this is desired
+ stop the units that are being disabled. If this is desired,
an additional <command>stop</command> command should be
executed afterwards.</para>
enabled (as with <command>enable</command>). Returns an exit
code of 0 if at least one is enabled, non-zero
otherwise. Prints the current enable status. To suppress
- this output use <option>--quiet</option>.</para>
+ this output, use <option>--quiet</option>.</para>
</listitem>
</varlistentry>
policy files. This has the same effect as
<command>disable</command> or <command>enable</command>,
depending how the unit is listed in the preset files. For
- more information on preset policy format see
+ more information on the preset policy format, see
<citerefentry><refentrytitle>systemd.preset</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
- For more information on the concept of presets please
+ For more information on the concept of presets, please
consult the
<ulink url="http://freedesktop.org/wiki/Software/systemd/Preset">Preset</ulink>
document.</para>
undone with <command>disable</command>. The effect of this
command is that a unit file is available for
<command>start</command> and other commands although it
- isn't installed directly in the unit search path.</para>
+ is not installed directly in the unit search path.</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><command>load <replaceable>NAME</replaceable>...</command></term>
+ <term><command>get-default</command></term>
<listitem>
- <para>Load one or more units specified on the command
- line. This will simply load their configuration from disk,
- but not start them. To start them you need to use the
- <command>start</command> command which will implicitly load
- a unit that has not been loaded yet. Note that systemd
- garbage collects loaded units that are not active or
- referenced by an active unit. This means that units loaded
- this way will usually not stay loaded for long. Also note
- that this command cannot be used to reload unit
- configuration. Use the <command>daemon-reload</command>
- command for that. All in all, this command is of little use
- except for debugging.</para>
+ <para>Get the default target specified
+ via <filename>default.target</filename> link.</para>
+ </listitem>
+ </varlistentry>
- <para>This command should not be confused with the
- <command>daemon-reload</command> or
- <command>reload</command>.</para>
+ <varlistentry>
+ <term><command>set-default <replaceable>NAME</replaceable></command></term>
+
+ <listitem>
+ <para>Set the default target to boot into. Command links
+ <filename>default.target</filename> to the given unit.</para>
</listitem>
</varlistentry>
+
<varlistentry>
<term><command>list-jobs</command></term>
<listitem>
<para>Cancel one or more jobs specified on the command line
- by their numeric job IDs. If no job id is specified, cancel
+ by their numeric job IDs. If no job ID is specified, cancel
all pending jobs.</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term><command>dump</command></term>
- <listitem>
- <para>Dump server status. This will output a (usually very
- long) human readable manager status dump. Its format is
- subject to change without notice and should not be parsed by
- applications.</para>
- </listitem>
- </varlistentry>
<varlistentry>
<term><command>list-dependencies <replaceable>NAME</replaceable></command></term>
<listitem>
<para>Shows required and wanted units of the specified
- unit. If no unit is specified
+ unit. If no unit is specified,
<filename>default.target</filename> is implied. Target units
are recursively expanded. When <option>--all</option> is
- passed all other units are recursively expanded as
+ passed, all other units are recursively expanded as
well.</para>
</listitem>
</varlistentry>
<listitem>
<para>Create a snapshot. If a snapshot name is specified,
the new snapshot will be named after it. If none is
- specified an automatic snapshot name is generated. In either
+ specified, an automatic snapshot name is generated. In either
case, the snapshot name used is printed to STDOUT, unless
<option>--quiet</option> is specified.</para>
<para>A snapshot refers to a saved state of the systemd
manager. It is implemented itself as a unit that is
generated dynamically with this command and has dependencies
- on all units active at the time. At a later time the user
+ on all units active at the time. At a later time, the user
may return to this state by using the
<command>isolate</command> command on the snapshot unit.
</para>
state again. This command is of little use except for
debugging and package upgrades. Sometimes it might be
helpful as a heavy-weight <command>daemon-reload</command>.
- While the daemon is reexecuted all sockets systemd listens
- on on behalf of user configuration will stay accessible.
+ While the daemon is reexecuted, all sockets systemd listening
+ on behalf of user configuration will stay accessible.
</para>
</listitem>
</varlistentry>
<listitem>
<para>Unset one or more systemd manager environment
- variables. If only a variable name is specified it will be
+ variables. If only a variable name is specified, it will be
removed regardless of its value. If a variable and a value
- are specified the variable is only removed if it has the
+ are specified, the variable is only removed if it has the
specified value.</para>
</listitem>
</varlistentry>
<listitem>
<para>Enter default mode. This is mostly equivalent to
- <command>start default.target</command>.</para>
+ <command>isolate default.target</command>.</para>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>Enter rescue mode. This is mostly equivalent to
- <command>isolate rescue.target</command> but also prints a
+ <command>isolate rescue.target</command>, but also prints a
wall message to all users.</para>
</listitem>
</varlistentry>
<listitem>
<para>Enter emergency mode. This is mostly equivalent to
- <command>isolate emergency.target</command> but also prints
+ <command>isolate emergency.target</command>, but also prints
a wall message to all users.</para>
</listitem>
</varlistentry>
<term><command>halt</command></term>
<listitem>
- <para>Shut down and halt the system. This is mostly
- equivalent to <command>start halt.target</command> but also
+ <para>Shut down and halt the system. This is mostly equivalent to
+ <command>start halt.target --irreversible</command>, but also
prints a wall message to all users. If combined with
- <option>--force</option> shutdown of all running services is
+ <option>--force</option>, shutdown of all running services is
skipped, however all processes are killed and all file
systems are unmounted or mounted read-only, immediately
followed by the system halt. If <option>--force</option> is
- specified twice the operation is immediately executed
+ specified twice, the operation is immediately executed
without terminating any processes or unmounting any file
systems. This may result in data loss.</para>
</listitem>
<listitem>
<para>Shut down and power-off the system. This is mostly
- equivalent to <command>start poweroff.target</command> but
- also prints a wall message to all users. If combined with
- <option>--force</option> shutdown of all running services is
+ equivalent to <command>start poweroff.target --irreversible</command>,
+ but also prints a wall message to all users. If combined with
+ <option>--force</option>, shutdown of all running services is
skipped, however all processes are killed and all file
systems are unmounted or mounted read-only, immediately
followed by the powering off. If <option>--force</option> is
- specified twice the operation is immediately executed
+ specified twice, the operation is immediately executed
without terminating any processes or unmounting any file
systems. This may result in data loss.</para>
</listitem>
<listitem>
<para>Shut down and reboot the system. This is mostly
- equivalent to <command>start reboot.target</command> but
- also prints a wall message to all users. If combined with
- <option>--force</option> shutdown of all running services is
+ equivalent to <command>start reboot.target --irreversible</command>,
+ but also prints a wall message to all users. If combined with
+ <option>--force</option>, shutdown of all running services is
skipped, however all processes are killed and all file
systems are unmounted or mounted read-only, immediately
followed by the reboot. If <option>--force</option> is
- specified twice the operation is immediately executed
+ specified twice, the operation is immediately executed
without terminating any processes or unmounting any file
systems. This may result in data loss.</para>
</listitem>
<listitem>
<para>Shut down and reboot the system via kexec. This is
- mostly equivalent to <command>start kexec.target</command>
+ mostly equivalent to <command>start kexec.target --irreversible</command>,
but also prints a wall message to all users. If combined
- with <option>--force</option> shutdown of all running
+ with <option>--force</option>, shutdown of all running
services is skipped, however all processes are killed and
all file systems are unmounted or mounted read-only,
immediately followed by the reboot.</para>
new system manager process below it. This is intended for
usage in initial RAM disks ("initrd"), and will transition
from the initrd's system manager process (a.k.a "init"
- process) to the main system manager process. Takes two
- arguments: the directory to make the new root directory, and
+ process) to the main system manager process. This call takes two
+ arguments: the directory that is to become the new root directory, and
the path to the new system manager binary below it to
execute as PID 1. If the latter is omitted or the empty
string, a systemd binary will automatically be searched for
and used as init. If the system manager path is omitted or
- equal to the empty string the state of the initrd's system
+ equal to the empty string, the state of the initrd's system
manager process is passed to the main system manager, which
allows later introspection of the state of the services
involved in the initrd boot.</para>
<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>
<citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>loginctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
+ <citerefentry><refentrytitle>systemd.cgroupq</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry><refentrytitle>wall</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.preset</refentrytitle><manvolnum>5</manvolnum></citerefentry>
~ianmdlvl / elogind.git / blobdiff