X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.service.xml;h=a82dfb2c86496c11eb14f702ec0ece5c7f16b62a;hp=e584a1f006f54c5062cc31f65e3e2a2a5aab9146;hb=84b5b79a8f7b423c5b7cad4170eb68d57fe5e26c;hpb=96fb8242cc1ef6b0e28f6c86a4f57950095dd7f1
diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index e584a1f00..a82dfb2c8 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -307,6 +307,46 @@
+
+ BusPolicy=
+
+ If specfied, a custom kdbus
+ endpoint will be created and installed as the
+ default bus node for the service. Such a custom
+ endpoint can hold an own set of policy rules
+ that are enforced on top of the bus-wide ones.
+ The custom endpoint is named after the service
+ it was created for, and its node will be
+ bind-mounted over the default bus node
+ location, so the service can only access the
+ bus through its own endpoint. Note that custom
+ bus endpoints default to a 'deny all' policy.
+ Hence, if at least one
+ BusPolicy= directive is
+ given, you have to make sure to add explicit
+ rules for everything the service should be able
+ to do.
+ The value of this directive is comprised
+ of two parts; the bus name, and a verb to
+ specify to granted access, which is one of
+ ,
+ or
+ .
+ implies
+ , and
+ implies both and
+ .
+ If multiple access levels are specified for the
+ same bus name, the most powerful one takes
+ effect.
+
+ Examples:
+ BusPolicy=org.freedesktop.systemd1 talk
+ BusPolicy=org.foo.bar see
+ This option is only available on kdbus enabled systems.
+
+
+
ExecStart=Commands with their
@@ -1131,29 +1171,49 @@ ExecStart=/bin/echo $ONE $TWO ${TWO}
hit. Takes one of
,
,
- , or
- . If
- is set,
- hitting the rate limit will trigger no
- action besides that the start will not
- be permitted.
+ ,
+ ,
+ ,
+ or
+ . If
+ is set, hitting
+ the rate limit will trigger no action
+ besides that the start will not be
+ permitted.
causes a reboot following the normal
shutdown procedure (i.e. equivalent to
systemctl reboot).
- causes
- a forced reboot which will terminate
- all processes forcibly but should
- cause no dirty file systems on reboot
+ causes a
+ forced reboot which will terminate all
+ processes forcibly but should cause no
+ dirty file systems on reboot
(i.e. equivalent to systemctl
reboot -f) and
causes immediate execution of the
reboot2
system call, which might result in
- data loss. Defaults to
+ data loss. Similar,
+ ,
+ ,
+
+ have the effect of powering down the
+ system with similar
+ semantics. Defaults to
.
+
+ FailureAction=
+ Configure the action
+ to take when the service enters a failed
+ state. Takes the same values as
+ StartLimitAction=
+ and executes the same actions.
+ Defaults to .
+
+
+
RebootArgument=Configure the optional
@@ -1161,23 +1221,13 @@ ExecStart=/bin/echo $ONE $TWO ${TWO}
reboot2
system call if
StartLimitAction=
+ or FailureAction=
is a reboot action. This works just
like the optional argument to
systemctl reboot
command.
-
- FailureAction=
- Configure the action
- to take when the service enters a failed
- state. Takes the same values as
- StartLimitAction=
- and executes the same actions.
- Defaults to .
-
-
-
Check
@@ -1226,7 +1276,7 @@ ExecStart=/bin/echo $ONE $TWO ${TWO}
See Alsosystemd1,
- systemctl8,
+ systemctl1,
systemd.unit5,
systemd.exec5,
systemd.resource-control5,