X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.unit.xml;h=9c4269f3d2626ab1fbc5ead97a4e8f5378329768;hb=ba60f9054e7aee0b817cfef4f715b0022818bbb3;hp=81634410c15244d4f529cf8cc3e02c4bf55eacb5;hpb=0d624a785aed0423ee87f70d33de97df9662844b;p=elogind.git
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index 81634410c..9c4269f3d 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -56,7 +56,8 @@
systemd.swap,
systemd.target,
systemd.path,
- systemd.timer
+ systemd.timer,
+ systemd.snapshot
@@ -94,7 +95,7 @@
additional information in the unit files.
Boolean arguments used in unit files can be
- written in various forms. For positive settings the
+ written in various formats. For positive settings the
strings , ,
and are
equivalent. For negative settings the strings
@@ -105,7 +106,7 @@
Time span values encoded in unit files can be
written in various formats. A stand-alone number
specifies a time in seconds. If suffixed with a time
- unit, the unit is honored. A concatentation of
+ unit, the unit is honored. A concatenation of
multiple value with units is supported, in which case
the values are added up. Example: "50" refers to 50
seconds; "2min 200ms" refers to 2 minutes plus 200
@@ -144,6 +145,47 @@
activation which makes dependencies implicit, which
both results in a simpler and more flexible
system.
+
+ Some unit names reflect paths existing in the
+ file system name space. Example: a device unit
+ dev-sda.device refers to a device
+ with the device node /dev/sda in
+ the file system namespace. If this applies a special
+ way to escape the path name is used, so that it is
+ usable as part of a file name. Basically, given a
+ path, "/" is replaced by "-", and all unprintable
+ characters and the "-" are replaced by C-style "\x20"
+ escapes. The root directory "/" is encoded as single
+ dash, while otherwise the initial and ending "/" is
+ removed from all paths during transformation. This
+ escaping is reversible.
+
+ Optionally, units may be instantiated from a
+ template file at runtime. This allows creation of
+ multiple units from a single configuration file. If
+ systemd looks for a unit configuration file it will
+ first search for the literal unit name in the
+ filesystem. If that yields no success and the unit
+ name contains an @ character, systemd will look for a
+ unit template that shares the same name but with the
+ instance string (i.e. the part between the @ character
+ and the suffix) removed. Example: if a service
+ getty@tty3.service is requested
+ and no file by that name is found, systemd will look
+ for getty@.service and
+ instantiate a service from that configuration file if
+ it is found. To refer to the instance string from
+ within the configuration file you may use the special
+ %i specifier in many of the
+ configuration options. Other specifiers that may be
+ used are %n, %N,
+ %p, %P and
+ %I, for the full unit name, the
+ unescaped unit name, the prefix name, the unescaped
+ prefix name and the unescaped instance name,
+ respectively. The prefix name here refers to the
+ string before the @, i.e. "getty" in the example
+ above, where "tty3" is the instance name.
@@ -423,7 +465,7 @@
Alias=
- Additional names, this
+ Additional names this
unit shall be installed under. The
names listed here must have the same
suffix (i.e. type) as the unit file
@@ -468,7 +510,7 @@
effect that when the listed unit name
is activated the unit listing it is
activated
- to. WantedBy=foo.service
+ too. WantedBy=foo.service
in a service
bar.service is
mostly equivalent to
@@ -508,7 +550,8 @@
systemd.swap5,
systemd.target5,
systemd.path5,
- systemd.timer5
+ systemd.timer5,
+ systemd.snapshot5