X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.unit.xml;h=1b71538c8294f3a10ba54fa1a685f9e6130a266c;hb=42539b5e38eebd54173c6064ec394ccc3054a8ad;hp=a870f6b17ab325ab79c6c3254356a18e90d8296b;hpb=479fe882ae92e4c2eac3c995cd0d23d4c604889f;p=elogind.git
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index a870f6b17..1b71538c8 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -60,7 +60,9 @@
target.target,
path.path,
timer.timer,
- snapshot.snapshot
+ snapshot.snapshot,
+ slice.slice,
+ scope.scope/etc/systemd/system/*/run/systemd/system/*
@@ -81,12 +83,15 @@
A unit configuration file encodes information
about a service, a socket, a device, a mount point, an
automount point, a swap file or partition, a start-up
- target, a file system path, or a timer controlled and
- supervised by
- systemd1. The
- syntax is inspired by systemd1,
+ a temporary system state snapshot, a resource
+ management slice or a group of externally created
+ processes. The syntax is inspired by XDG
- Desktop Entry Specification.desktop files, which are in turn
+ Desktop Entry Specification
+ .desktop files, which are in turn
inspired by Microsoft Windows
.ini files.
@@ -110,6 +115,8 @@
systemd.path5,
systemd.timer5,
systemd.snapshot5.
+ systemd.slice5.
+ systemd.scope5.
Unit files are loaded from a set of paths
@@ -285,7 +292,7 @@
Local configuration
- /run/systemd/systemd
+ /run/systemd/systemVolatile units
@@ -310,7 +317,7 @@
- Load path when running in session mode ().
+ Load path when running in user mode ().
@@ -969,6 +976,7 @@
xen,
bochs,
chroot,
+ uml,
openvz,
lxc,
lxc-libvirt,
@@ -1115,19 +1123,46 @@
WantedBy=RequiredBy=
- Installs a symlink in
- the .wants/
- or .requires/
- subdirectory for a unit, respectively. This has the
- effect that when the listed unit name
- is activated the unit listing it is
- activated
- too. WantedBy=foo.service
+ A symbolic link is
+ created in the
+ .wants/ or
+ .requires/ directory
+ of the listed unit when this unit is
+ activated by systemctl
+ enable. This has the effect
+ that a dependency of type
+ Wants= or
+ Requires= is added
+ from the listed unit to the current
+ unit. The primary result is that the
+ current unit will be started when the
+ listed unit is started. See the
+ description of
+ Wants= and
+ Requires= in the
+ [Unit] section for details.
+
+ WantedBy=foo.service
in a service
bar.service is
mostly equivalent to
Alias=foo.service.wants/bar.service
- in the same file.
+ in the same file. In case of template
+ units, systemctl enable
+ must be called with an instance name, and
+ this instance will be added to the
+ .wants/ or
+ .requires/ list
+ of the listed unit.
+ E.g. WantedBy=getty.target
+ in a service
+ getty@.service
+ will result in systemctl
+ enable getty@tty2.service
+ creating a
+ getty.target.wants/getty@tty2.service
+ link to getty@.service.
+
@@ -1147,7 +1182,7 @@
The following specifiers are interpreted in the
- Install section: %n, %N, %p, %i, %U, %u, %m, %H, %b.
+ Install section: %n, %N, %p, %i, %U, %u, %m, %H, %b, %v.
For their meaning see the next section.
@@ -1265,6 +1300,11 @@
Host nameThe hostname of the running system.
+
+ %v
+ Kernel release
+ Identical to uname -r output.
+ %%Escaped %
@@ -1291,9 +1331,12 @@
systemd.path5,
systemd.timer5,
systemd.snapshot5,
+ systemd.scope5,
+ systemd.slice5,
systemd.time7,
capabilities7,
- systemd.directives7
+ systemd.directives7,
+ uname1