X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.unit.xml;h=c3c9561f2fb1412a43a11dd6454969f9696ce36d;hb=424313503a6813bd78a7e8524668044ab61f3fb3;hp=bb11682fc62e560bff7170d23291d42136bb0232;hpb=b5e9dba8d60b8fb80b6302b6ea2cd665b3ab370c;p=elogind.git
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index bb11682fc..c3c9561f2 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -189,6 +189,11 @@
respectively. The prefix name here refers to the
string before the @, i.e. "getty" in the example
above, where "tty3" is the instance name.
+
+ The unit file format is covered by the
+ Interface
+ Stability Promise.
@@ -418,8 +423,9 @@
Lists one or more
units that are activated when this
- unit fails (i.e. enters maintenance
- state).
+ unit enters the
+ 'failed'
+ state.
@@ -484,6 +490,23 @@
.
+
+ AllowIsolate=
+
+ Takes a boolean
+ argument. If
+ this unit may be used with the
+ systemctl isolate
+ command. Otherwise this will be
+ refused. It probably is a good idea to
+ leave this disabled except for target
+ units that shall be used similar to
+ runlevels in SysV init systems, just
+ as a precaution to avoid unusable
+ system states. This option defaults to
+ .
+
+
DefaultDependencies=
@@ -535,22 +558,23 @@
time. If this time limit is reached
the job will be cancelled, the unit
however will not change state or even
- enter maintenance mode. This value
- defaults to 0 (job timeouts disabled),
- except for device units. NB: this
- timeout is independent from any
- unit-specific timeout (for example,
- the timeout set with
+ enter the 'failed'
+ mode. This value defaults to 0 (job
+ timeouts disabled), except for device
+ units. NB: this timeout is independent
+ from any unit-specific timeout (for
+ example, the timeout set with
Timeout= in service
- units) as the job timeout has no effect
- on the unit itself, only on the job
- that might be pending for it. Or in
- other words: unit-specific timeouts
+ units) as the job timeout has no
+ effect on the unit itself, only on the
+ job that might be pending for it. Or
+ in other words: unit-specific timeouts
are useful to abort unit state
changes, and revert them. The job
timeout set with this option however
- is useful to abort only the job waiting
- for the unit state to change.
+ is useful to abort only the job
+ waiting for the unit state to
+ change.