systemd/test/units/TEST-07-PID1.exec-timestamps.sh

#!/usr/bin/env bash
# SPDX-License-Identifier: LGPL-2.1-or-later
set -eux
set -o pipefail

# Check that timestamps of a Type=notify service are consistent

systemd-run --service-type notify --property NotifyAccess=all --unit notify.service --wait sh -c 'systemd-notify --ready; exit 1' || :

start=$(systemctl show --property=ExecMainStartTimestampMonotonic --value notify.service)
handoff=$(systemctl show --property=ExecMainHandoffTimestampMonotonic --value notify.service)
active=$(systemctl show --property=ActiveEnterTimestampMonotonic --value notify.service)
exit=$(systemctl show --property=ExecMainExitTimestampMonotonic --value notify.service)

[[ $start -le $handoff ]]
[[ $handoff -le $active ]]
[[ $active -le $exit ]]
core: add ExecMainHandoverTimestamp property recording time-of-execve Enable the exec_fd logic for Type=notify* services too, and change it to send a timestamp instead of a '1' byte. Record the timestamp in a new ExecMainHandoverTimestamp property so that users can track accurately when control is handed over from systemd to the service payload, so that latency and startup performance can be trivially and accurately tracked and attributed. 2024-04-20 00:50:16 +01:00			`#!/usr/bin/env bash`
			`# SPDX-License-Identifier: LGPL-2.1-or-later`
			`set -eux`
			`set -o pipefail`

			`# Check that timestamps of a Type=notify service are consistent`

			`systemd-run --service-type notify --property NotifyAccess=all --unit notify.service --wait sh -c 'systemd-notify --ready; exit 1' \|\| :`

			`start=$(systemctl show --property=ExecMainStartTimestampMonotonic --value notify.service)`
manager: switch service unit type over to using new handoff timestamping logic Also: rename Handover → Handoff. I think it makes it clearer that this is not really about handing over any resources, but that the executor is out off the game from that point on. 2024-04-23 23:27:23 +02:00			`handoff=$(systemctl show --property=ExecMainHandoffTimestampMonotonic --value notify.service)`
core: add ExecMainHandoverTimestamp property recording time-of-execve Enable the exec_fd logic for Type=notify* services too, and change it to send a timestamp instead of a '1' byte. Record the timestamp in a new ExecMainHandoverTimestamp property so that users can track accurately when control is handed over from systemd to the service payload, so that latency and startup performance can be trivially and accurately tracked and attributed. 2024-04-20 00:50:16 +01:00			`active=$(systemctl show --property=ActiveEnterTimestampMonotonic --value notify.service)`
			`exit=$(systemctl show --property=ExecMainExitTimestampMonotonic --value notify.service)`

manager: switch service unit type over to using new handoff timestamping logic Also: rename Handover → Handoff. I think it makes it clearer that this is not really about handing over any resources, but that the executor is out off the game from that point on. 2024-04-23 23:27:23 +02:00			`[[ $start -le $handoff ]]`
			`[[ $handoff -le $active ]]`
core: add ExecMainHandoverTimestamp property recording time-of-execve Enable the exec_fd logic for Type=notify* services too, and change it to send a timestamp instead of a '1' byte. Record the timestamp in a new ExecMainHandoverTimestamp property so that users can track accurately when control is handed over from systemd to the service payload, so that latency and startup performance can be trivially and accurately tracked and attributed. 2024-04-20 00:50:16 +01:00			`[[ $active -le $exit ]]`