man: also fix documentation of start-limit-hit

(cherry picked from commit 390dffb862af5791a33abef08011f87818249975)

diff --git a/man/org.freedesktop.systemd1.xml b/man/org.freedesktop.systemd1.xml
index 9cd6a69311a97ee53f17a64bc03c9aff4aa375fa..ec38613da08de9d91d18235143e6eda8da6864ea 100644 (file)
--- a/man/org.freedesktop.systemd1.xml
+++ b/man/org.freedesktop.systemd1.xml
@@ -4818,9 +4818,10 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
       code. <literal>signal</literal> indicates that a service process exited with an uncaught
       signal. <literal>core-dump</literal> indicates that a service process exited uncleanly and dumped
       core. <literal>watchdog</literal> indicates that a service did not send out watchdog ping messages
-      often enough. <literal>start-limit</literal> indicates that a service has been started too frequently
-      in a specific time frame (as configured in <varname>StartLimitInterval</varname>,
-      <varname>StartLimitBurst</varname>).</para>
+      often enough. <literal>start-limit-hit</literal> indicates that a service has been started too
+      frequently in a specific time frame (as configured in <varname>StartLimitInterval</varname>,
+      <varname>StartLimitBurst</varname>). <literal>oom-kill</literal> indicates that a service was
+      terminated due to an out-of-memory (OOM) situation.</para>
 
       <para><varname>ControlGroup</varname> indicates the control group path the processes of this service
       unit are placed in.</para>