X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.unit.xml;h=da2dba52b3510d4d2d257d6959e06aa0003f5f03;hp=123965bd4477870e93e818b9efef97e2be054ec4;hb=abdf7993161a2762df6887fdb5a5f0f4f5da24cf;hpb=1b64d026af01277e332d10d9e67e2eed5a4ded28
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index 123965bd4..da2dba52b 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -44,7 +44,7 @@
systemd.unit
- systemd unit configuration files
+ Unit configuration
@@ -258,6 +258,21 @@
Runtime socket dir
This is either /run (for the system manager) or $XDG_RUNTIME_DIR (for user managers).
+
+ %u
+ User name
+ This is the name of the configured user of the unit, or (if none is set) the user running the systemd instance.
+
+
+ %h
+ User home directory
+ This is the home directory of the configured user of the unit, or (if none is set) the user running the systemd instance.
+
+
+ %s
+ User shell
+ This is the shell of the configured user of the unit, or (if none is set) the user running the systemd instance.
+
@@ -348,7 +363,15 @@
Requires= in order
to achieve a system that is more
robust when dealing with failing
- services.
+ services.
+
+ Note that dependencies of this
+ type may also be configured outside of
+ the unit configuration file by
+ adding a symlink to a
+ .requires/ directory
+ accompanying the unit file. For
+ details see above.
@@ -400,7 +423,9 @@
the transaction as a whole. This is
the recommended way to hook start-up
of one unit to the start-up of another
- unit. Note that dependencies of this
+ unit.
+
+ Note that dependencies of this
type may also be configured outside of
the unit configuration file by
adding a symlink to a
@@ -410,7 +435,7 @@
- BindTo=
+ BindsTo=
Configures requirement
dependencies, very similar in style to
@@ -426,6 +451,21 @@
systemd.
+
+ PartOf=
+
+ Configures dependencies
+ similar to Requires=,
+ but limited to stopping and restarting
+ of units. When systemd stops or restarts
+ the units listed here, the action is
+ propagated to this unit.
+ Note that this is a one way dependency -
+ changes to this unit do not affect the
+ listed units.
+
+
+
Conflicts=
@@ -527,8 +567,8 @@
- PropagateReloadTo=
- PropagateReloadFrom=
+ PropagatesReloadTo=
+ ReloadPropagatedFrom=
Lists one or more
units where reload requests on the
@@ -869,35 +909,6 @@
symlinks.
-
- Names=
-
- Additional names for
- this unit. The names listed here must
- have the same suffix (i.e. type) as
- the unit file name. This option may be
- specified more than once, in which
- case all listed names are used. Note
- that this option is different from the
- Alias= option from
- the [Install] section mentioned
- below. See below for details. Note
- that in almost all cases this option
- is not what you want. A symlink alias
- in the file system is generally
- preferable since it can be used as
- lookup key. If a unit with a symlinked
- alias name is not loaded and needs to
- be it is easily found via the
- symlink. However, if a unit with an
- alias name configured with this
- setting is not loaded it will not be
- discovered. This settings' only use is
- in conjunction with service
- instances.
-
-
-
SourcePath=
A path to a
@@ -936,30 +947,7 @@
time,
systemctl enable
will create symlinks from these names
- to the unit file name. Note that this
- is different from the
- Names= option from
- the [Unit] section mentioned above:
- The names from
- Names= apply
- unconditionally if the unit is
- loaded. The names from
- Alias= apply only
- if the unit has actually been
- installed with the
- systemctl enable
- command. Also, if systemd searches for a
- unit, it will discover symlinked alias
- names as configured with
- Alias=, but not
- names configured with
- Names= only. It is
- a common pattern to list a name in
- both options. In this case, a unit
- will be active under all names if
- installed, but also if not installed
- but requested explicitly under its
- main name.
+ to the unit file name.