X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemctl.xml;h=7f1e98f5c5472f84095b345514ffd417b03481d1;hb=fa57130d35dd8fd8c3f2f2126dd7fc6930a08e35;hp=b043581be0ca5a5c33dccfc2aef919bc8584df6b;hpb=79640424059328268b9fb6c5fa8eb777b27a177e;p=elogind.git
diff --git a/man/systemctl.xml b/man/systemctl.xml
index b043581be..7f1e98f5c 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -63,6 +63,19 @@ along with systemd; If not, see .
introspect and control the state of the
systemd1
system and service manager.
+
+ For unit commands, the NAME represents full name of the unit.
+
+systemctl start foo.service
+
+ For unit file commands, the NAME represents the full name of the unit file, or the absolute path to the unit file.
+
+systemctl start /path/to/foo.service
+
+ While working with services/service files, systemctl implicitly appends the ".service" suffix when it is missing.
+
+systemctl start foo
+
@@ -174,7 +187,7 @@ along with systemd; If not, see .
- Do not ellipsize unit names, cgroup members, and
+ Do not ellipsize unit names, process tree entries, and
truncate unit descriptions in the output of
list-units and
list-jobs.
@@ -444,7 +457,7 @@ along with systemd; If not, see .
- Execute operation remotely. Specify a hostname, or
+ Execute the operation remotely. Specify a hostname, or
username and hostname separated by @, to connect to. This
will use SSH to talk to the remote systemd
instance.
@@ -711,14 +724,14 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
Set the specified unit properties at runtime where
this is supported. This allows changing configuration
- parameter properties such as resource management controls at
+ parameter properties such as resource control settings at
runtime. Not all properties may be changed at runtime, but
- many resource management settings (primarily those in
- systemd.cgroup5)
+ many resource control settings (primarily those in
+ systemd.resource-control5)
may. The changes are applied instantly, and stored on disk
for future boots, unless is
- passed, in which case the settings only apply until the next
- reboot. The syntax of the property assignment follows
+ 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.Example: systemctl set-property foobar.service CPUShares=777
@@ -830,10 +843,11 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
case of socket units), and so on.Depending on whether ,
- or is
- 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
+ , ,
+ or is specified, this enables the unit
+ for the system, for the calling user only, for only this boot of
+ the system, or for all future logins of all users, or only this
+ boot. Note that in the last case, no systemd daemon
configuration is reloaded.
@@ -860,8 +874,9 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
This command honors ,
- , in a
- similar way as enable.
+ , and
+ in a similar way as
+ enable.
@@ -918,7 +933,9 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
start them. This is a stronger version of
disable, since it prohibits all kinds of
activation of the unit, including manual activation. Use
- this option with care.
+ this option with care. This honors the
+ option to only mask temporarily
+ until the next reoobt of the system.
@@ -1162,7 +1179,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- reboot
+ reboot argShut down and reboot the system. This is mostly
@@ -1175,6 +1192,16 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
specified twice, the operation is immediately executed
without terminating any processes or unmounting any file
systems. This may result in data loss.
+
+ If the optional argument
+ arg is given, it will be passed
+ as the optional argument to the
+ reboot2
+ system call. The value is architecture and firmware
+ specific. As an example, recovery might
+ be used to trigger system recovery, and
+ fota might be used to trigger a
+ firmware over the air update.
@@ -1286,7 +1313,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
journalctl1,
loginctl1,
systemd.unit5,
- systemd.cgroup5,
+ systemd.resource-management5,
systemd.special7,
wall1,
systemd.preset5