X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemctl.xml;h=ed1bf4813ae90376eff9c8f42827ac979a877626;hb=0d3f7bb3a5bc6d5c0712f88a080fed388981bca3;hp=250866a875ec754d24ffcb26d20136dd05cec9c5;hpb=e0e009c067aa7237f9683c46e5845bbb11ec67c2;p=elogind.git
diff --git a/man/systemctl.xml b/man/systemctl.xml
index 250866a87..ed1bf4813 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -580,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
@@ -596,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
@@ -617,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
@@ -626,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
@@ -637,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,
@@ -646,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,
@@ -676,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
@@ -687,7 +696,7 @@ 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
@@ -698,7 +707,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- is-failed NAME...
+ is-failed PATTERN...
Check whether any of the specified units are in a "failed" state.
@@ -709,7 +718,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- status NAME...|PID...]
+ status PATTERN...|PID...]
Show terse runtime status information about one or
@@ -735,7 +744,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- show NAME...|JOB...
+ show PATTERN...|JOB...
Show properties of one or more units, jobs, or the
@@ -752,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
@@ -788,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
@@ -798,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
@@ -978,7 +987,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
static
Unit is not enabled, but has no provisions for enabling in [Install] section
- 1
+ 0
disabled
@@ -1137,7 +1146,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
- delete NAME...
+ delete PATTERN...
Remove a snapshot previously created with
@@ -1181,6 +1190,19 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
specified value.
+
+ import-environment VARIABLE...
+
+
+ Import all, one or more environment variables set on
+ the client into the systemd manager environment block. If
+ no arguments are passed the entire environment block is
+ imported. Otherwise a list of one or more environment
+ variable names should be passed, whose client side values
+ are then imported into the manager's environment
+ block.
+
+
@@ -1383,23 +1405,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
+
@@ -1441,6 +1495,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
systemd.special7,
wall1,
systemd.preset5
+ glob7