X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemctl.xml;h=13a4444a0437e16aecd274d2282a65c1cd59ea0e;hb=a9a305332b7faf0d0d16db04909badaf6a095fef;hp=5e55f29287051c154d4c5d7cae903e89096dda62;hpb=171754aa4ae37a6ab626878256f7b664da78ef55;p=elogind.git
diff --git a/man/systemctl.xml b/man/systemctl.xml
index 5e55f2928..13a4444a0 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -174,10 +174,11 @@ along with systemd; If not, see .
- Do not ellipsize unit names, process tree entries, and
- truncate unit descriptions in the output of
- list-units and
- list-jobs.
+ Do not ellipsize unit names, process tree entries,
+ journal output, or truncate unit descriptions in the output
+ of status, list-units,
+ list-jobs, and
+ list-timers.
@@ -193,8 +194,8 @@ along with systemd; If not, see .
- When queuing a new job, control how to deal with already
- queued jobs. Takes one of fail,
+ When queuing a new job, this option controls how to deal with
+ already queued jobs. It takes one of fail,
replace,
replace-irreversibly,
isolate,
@@ -237,7 +238,7 @@ along with systemd; If not, see .
applications.ignore-requirements is similar to
- ignore-dependencies but only causes the
+ ignore-dependencies, but only causes the
requirement dependencies to be ignored, the ordering
dependencies will still be honoured.
@@ -256,7 +257,7 @@ along with systemd; If not, see .
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 a list of active locks
+ (regardless of whether privileged or not) and a list of active locks
is printed. However, if
is specified, the locks are ignored and not printed, and the
operation attempted anyway, possibly requiring additional
@@ -294,7 +295,7 @@ along with systemd; If not, see .
- Do not print a legend, i.e. the column headers and
+ Do not print the legend, i.e. the column headers and
the footer with hints.
@@ -451,7 +452,7 @@ along with systemd; If not, see .
with identical immediate effects, however, since the latter
is lost on reboot, the changes are lost too.
- Similar, when used with
+ Similarly, when used with
set-property, make changes only
temporarily, so that they are lost on the next
reboot.
@@ -542,7 +543,7 @@ along with systemd; If not, see .
list-sockets PATTERN...
- List socket units ordered by the listening address.
+ List socket units ordered by listening address.
If one or more PATTERNs are
specified, only socket units matching one of them are
shown. Produces output similar to
@@ -579,15 +580,24 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- start NAME...
+ start PATTERN...Start (activate) one or more units specified on the
command line.
+
+ Note that glob patterns operate on a list of currently
+ loaded units. Units which are not active and are not in a
+ failed state usually are not loaded, and would not be
+ matched by any pattern. In addition, in case of
+ instantiated units, systemd is often unaware of the
+ instance name until the instance has been started. Therefore
+ using glob patterns with start
+ has limited usefulness.
- stop NAME...
+ stop PATTERN...Stop (deactivate) one or more units specified on the
@@ -595,7 +605,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- reload NAME...
+ reload PATTERN...Asks all units listed on the command line to reload
@@ -616,7 +626,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- restart NAME...
+ restart PATTERN...Restart one or more units specified on the command
@@ -625,7 +635,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- try-restart NAME...
+ try-restart PATTERN...Restart one or more units specified on the command
@@ -636,7 +646,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- reload-or-restart NAME...
+ reload-or-restart PATTERN...Reload one or more units if they support it. If not,
@@ -645,7 +655,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- reload-or-try-restart NAME...
+ reload-or-try-restart PATTERN...Reload one or more units if they support it. If not,
@@ -675,7 +685,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- kill NAME...
+ kill PATTERN...Send a signal to one or more processes of the
@@ -686,18 +696,18 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- is-active NAME...
+ is-active PATTERN...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
+ active, or non-zero otherwise. Unless
is specified, this will also print the current unit state to
STDOUT.
- is-failed NAME...
+ is-failed PATTERN...Check whether any of the specified units are in a "failed" state.
@@ -708,7 +718,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- statusNAME...|PID...]
+ statusPATTERN...|PID...]Show terse runtime status information about one or
@@ -719,12 +729,22 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
belongs to.This function is intended to generate human-readable
- output. If you are looking for computer-parsable output, use
- show instead.
+ output. If you are looking for computer-parsable output,
+ use show instead. By default this
+ function only shows 10 lines of output and ellipsizes
+ lines to fit in the terminal window. This can be changes
+ with and ,
+ see above. In addition, journalctl
+ --unit=NAME or
+ journalctl
+ --user-unit=NAME use
+ a similar filter for messages and might be more
+ convenient.
+
- showNAME...|JOB...
+ showPATTERN...|JOB...Show properties of one or more units, jobs, or the
@@ -741,7 +761,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- cat NAME...
+ cat PATTERN...Show backing files of one or more units. Prints the
@@ -777,7 +797,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- help NAME...|PID...
+ help PATTERN...|PID...Show manual pages for one or more units, if
@@ -787,7 +807,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- reset-failed [NAME...]
+ reset-failed [PATTERN...]Reset the failed state of the
@@ -967,7 +987,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
staticUnit is not enabled, but has no provisions for enabling in [Install] section
- 1
+ 0disabled
@@ -1126,7 +1146,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- delete NAME...
+ delete PATTERN...Remove a snapshot previously created with
@@ -1372,23 +1392,55 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
Parameter Syntax
- For unit commands the specified
- NAME should be the full name of the
- unit, or an abbreviated name which is automatically extended with
- the .service suffix.
- # systemctl start foo.service is equivalent to:
- # systemctl start foo
- Note that (absolute) paths to device nodes are automatically converted to device unit names, and other (absolute) paths to mount unit names.
- # systemctl status /dev/sda
-# systemctl status /home is equivalent to:
- # systemctl status dev-sda.device
-# systemctl status home.mount
-
- For unit file commands the
- specified NAME should be the full name
- of the unit file, or the absolute path to the unit file.
- # systemctl link /path/to/foo.service
-
+ Unit ommands listed above take either a single unit name
+ (designated as NAME), or multiple
+ unit specifications (designated as
+ PATTERN...). In the first case, the
+ unit name with or without a suffix must be given. If the suffix
+ is not specified, systemctl will append a suitable suffix,
+ .service by default, and a type-specific
+ suffix in case of commands which operate only on specific unit
+ types. For example,
+ # systemctl start sshd and
+ # systemctl start sshd.service
+ are equivalent, as are
+ # systemctl isolate snapshot-11
+ and
+ # systemctl isolate snapshot-11.snapshot
+ Note that (absolute) paths to device nodes are automatically
+ converted to device unit names, and other (absolute) paths to
+ mount unit names.
+ # systemctl status /dev/sda
+# systemctl status /home
+ are equivalent to:
+ # systemctl status dev-sda.device
+# systemctl status home.mount
+ In the second case, shell-style globs will be matched against
+ currently loaded units, and literal unit names, with or without
+ a suffix, will be treated as in the first case. This means that
+ literal unit names always refer to exactly one unit, but globs
+ may match zero units and this is not considered an error.
+
+ Glob patterns use
+ fnmatch3,
+ so normal shell-style globbing rules are used, and
+ *, ?,
+ [] may be used. See
+ glob7
+ for more details. The patterns are matched against the names of
+ currently loaded units, and patterns which don't match anything
+ are silently skipped. For example:
+ # systemctl stop sshd@*.service
+ will stop all sshd@.service instances.
+
+
+ For unit file commands, the specified
+ NAME should be the full name of the
+ unit file, or the absolute path to the unit file:
+ # systemctl enable foo.service
+ or
+ # systemctl link /path/to/foo.service
+
@@ -1430,6 +1482,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
systemd.special7,
wall1,
systemd.preset5
+ glob7