summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorJouke Witteveen <j.witteveen@gmail.com>2016-11-23 22:51:33 +0100
committerMartin Pitt <martin.pitt@ubuntu.com>2016-11-23 22:51:33 +0100
commite0c7d5f7be126961e03929b5db40ce960f3ebaaa (patch)
tree6f5896cf154452f2f68f951ab79492b71bb04950 /man
parentd6fceaf1f7ff765bdc3b135f3d3676ec689da312 (diff)
downloadsystemd-e0c7d5f7be126961e03929b5db40ce960f3ebaaa.tar.gz
man: document protocol error type for service failures (#4724)
Diffstat (limited to 'man')
-rw-r--r--man/systemd.exec.xml17
1 files changed, 9 insertions, 8 deletions
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index 03e55a7aff..abc275aad0 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -1771,14 +1771,15 @@
<listitem><para>Only defined for the service unit type, this environment variable is passed to all
<varname>ExecStop=</varname> and <varname>ExecStopPost=</varname> processes, and encodes the service
- "result". Currently, the following values are defined: <literal>timeout</literal> (in case of an operation
- timeout), <literal>exit-code</literal> (if a service process exited with a non-zero exit code; see
- <varname>$EXIT_CODE</varname> below for the actual exit code returned), <literal>signal</literal> (if a
- service process was terminated abnormally by a signal; see <varname>$EXIT_CODE</varname> below for the actual
- signal used for the termination), <literal>core-dump</literal> (if a service process terminated abnormally and
- dumped core), <literal>watchdog</literal> (if the watchdog keep-alive ping was enabled for the service but it
- missed the deadline), or <literal>resources</literal> (a catch-all condition in case a system operation
- failed).</para>
+ "result". Currently, the following values are defined: <literal>protocol</literal> (in case of a protocol
+ violation; if a service did not take the steps required by its configuration), <literal>timeout</literal> (in
+ case of an operation timeout), <literal>exit-code</literal> (if a service process exited with a non-zero exit
+ code; see <varname>$EXIT_CODE</varname> below for the actual exit code returned), <literal>signal</literal>
+ (if a service process was terminated abnormally by a signal; see <varname>$EXIT_CODE</varname> below for the
+ actual signal used for the termination), <literal>core-dump</literal> (if a service process terminated
+ abnormally and dumped core), <literal>watchdog</literal> (if the watchdog keep-alive ping was enabled for the
+ service but it missed the deadline), or <literal>resources</literal> (a catch-all condition in case a system
+ operation failed).</para>
<para>This environment variable is useful to monitor failure or successful termination of a service. Even
though this variable is available in both <varname>ExecStop=</varname> and <varname>ExecStopPost=</varname>, it