diff options
| author | micah <micah@riseup.net> | 2017-01-11 15:07:35 -0500 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2017-01-11 15:07:35 -0500 |
| commit | 6539dd7c42946d9ba5dc43028b8b5785eb2db3c5 (patch) | |
| tree | 84317393f7f008a0c108950daa0479b1aa21413f /man | |
| parent | 07f4efcc8a3511e28a895eb888bd0a7bebd1f99b (diff) | |
Document how restart actions work (#5052)
When a user is trying to understand what is going on with a restart action, it is useful to explicitly describe how the action is run. It may seem obvious, but it is helpful to be explicit so one knows there isn't a special ExecRestart= or similar option that they could be looking at.
Diffstat (limited to 'man')
| -rw-r--r-- | man/systemctl.xml | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/man/systemctl.xml b/man/systemctl.xml index acf975138a..1440d71925 100644 --- a/man/systemctl.xml +++ b/man/systemctl.xml @@ -760,18 +760,18 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service <term><command>restart <replaceable>PATTERN</replaceable>…</command></term> <listitem> - <para>Restart one or more units specified on the command - line. If the units are not running yet, they will be - started.</para> + <para>Stop and then start one or more units specified on the + command line. If the units are not running yet, they will + be started.</para> </listitem> </varlistentry> <varlistentry> <term><command>try-restart <replaceable>PATTERN</replaceable>…</command></term> <listitem> - <para>Restart one or more units specified on the command - line if the units are running. This does nothing if units are not - running.</para> + <para>Stop and then start one or more units specified on the + command line if the units are running. This does nothing + if units are not running.</para> <!-- Note that we don't document condrestart here, as that is just compatibility support, and we generally don't document that. --> </listitem> |