From: Luca Boccassi <bluca@debian.org>
Date: Tue, 23 Apr 2024 09:47:49 +0000 (+0100)
Subject: man: document service types that record ExecMainHandoverTimestamp
X-Git-Tag: v256-rc1~36
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c75c8a38b86dd6cd4fba168b2f7ab4cd3b71d66e;p=thirdparty%2Fsystemd.git

man: document service types that record ExecMainHandoverTimestamp

Follow-up for 93cb78aee2cff8109a5a70128287732f03d7a062
---

diff --git a/man/org.freedesktop.systemd1.xml b/man/org.freedesktop.systemd1.xml
index 749e6e3653e..ca8696bed5e 100644
--- a/man/org.freedesktop.systemd1.xml
+++ b/man/org.freedesktop.systemd1.xml
@@ -4716,11 +4716,12 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
       <varname>ExecMainStartTimestamp</varname> timestamps record when the main child process is spawned by
       the service manager. <varname>ExecMainExitTimestamp</varname> timestamps record when the main child
       process exit has been detected by the service manager. <varname>ExecMainHandoverTimestamp</varname>
-      timestamps record when the service executable is executed by <command>systemd-executor</command>.
-      This is often the same runtime information that is stored in <varname>ExecStart=</varname>. However,
-      it deviates for <varname>Type=forking</varname> services where the main process of the service is not
-      forked off systemd directly. These fields either contain information of the last run of the process or
-      of the current running process.</para>
+      timestamps record when the service executable is executed by <command>systemd-executor</command> for
+      services of type <literal>exec</literal>, <literal>dbus</literal>, <literal>notify</literal>, and
+      <literal>notify-reload</literal>. This is often the same runtime information that is stored in
+      <varname>ExecStart=</varname>. However, it deviates for <varname>Type=forking</varname> services where
+      the main process of the service is not forked off systemd directly. These fields either contain
+      information of the last run of the process or of the current running process.</para>
 
       <para><varname>MainPID</varname> and <varname>ControlPID</varname> contain the main and control PID of
       the service. The main PID is the current main PID of the service and is 0 when the service currently