1
0
mirror of https://github.com/systemd/systemd.git synced 2024-12-25 01:34:28 +03:00
systemd/test/units/testsuite-23.start-stop-no-reload.sh

94 lines
2.9 KiB
Bash
Executable File

#!/usr/bin/env bash
# SPDX-License-Identifier: LGPL-2.1-or-later
# -*- mode: shell-script; indent-tabs-mode: nil; sh-basic-offset: 4; -*-
# ex: ts=8 sw=4 sts=4 et filetype=sh
set -eux
set -o pipefail
# Test start & stop operations without daemon-reload
at_exit() {
set +e
rm -f /run/systemd/system/testsuite-23-no-reload.{service,target}
}
trap at_exit EXIT
cat >/run/systemd/system/testsuite-23-no-reload.target <<EOF
[Unit]
Wants=testsuite-23-no-reload.service
EOF
systemctl daemon-reload
systemctl start testsuite-23-no-reload.target
# The filesystem on the test image, despite being ext4, seems to have a mtime
# granularity of one second, which means the manager's unit cache won't be
# marked as dirty when writing the unit file, unless we wait at least a full
# second after the previous daemon-reload.
# May 07 23:12:20 H testsuite-48.sh[30]: + cat
# May 07 23:12:20 H testsuite-48.sh[30]: + ls -l --full-time /etc/systemd/system/testsuite-23-no-reload.service
# May 07 23:12:20 H testsuite-48.sh[52]: -rw-r--r-- 1 root root 50 2020-05-07 23:12:20.000000000 +0100 /
# May 07 23:12:20 H testsuite-48.sh[30]: + stat -f --format=%t /etc/systemd/system/testsuite-23-no-reload.servic
# May 07 23:12:20 H testsuite-48.sh[53]: ef53
sleep 3.1
cat >/run/systemd/system/testsuite-23-no-reload.service <<EOF
[Service]
ExecStart=/bin/sleep infinity
EOF
systemctl start testsuite-23-no-reload.service
systemctl is-active testsuite-23-no-reload.service
# Stop and remove, and try again to exercise https://github.com/systemd/systemd/issues/15992
systemctl stop testsuite-23-no-reload.service
rm -f /run/systemd/system/testsuite-23-no-reload.service
systemctl daemon-reload
sleep 3.1
cat >/run/systemd/system/testsuite-23-no-reload.service <<EOF
[Service]
ExecStart=/bin/sleep infinity
EOF
# Start a non-existing unit first, so that the cache is reloaded for an unrelated
# reason. Starting the existing unit later should still work thanks to the check
# for the last load attempt vs cache timestamp.
systemctl start testsuite-23-no-reload-nonexistent.service || true
systemctl start testsuite-23-no-reload.service
systemctl is-active testsuite-23-no-reload.service
# Stop and remove, and try again to exercise the transaction setup code path by
# having the target pull in the unloaded but available unit
systemctl stop testsuite-23-no-reload.service testsuite-23-no-reload.target
rm -f /run/systemd/system/testsuite-23-no-reload.service /run/systemd/system/testsuite-23-no-reload.target
systemctl daemon-reload
sleep 3.1
cat >/run/systemd/system/testsuite-23-no-reload.target <<EOF
[Unit]
Conflicts=shutdown.target
Wants=testsuite-23-no-reload.service
EOF
systemctl daemon-reload
systemctl start testsuite-23-no-reload.target
cat >/run/systemd/system/testsuite-23-no-reload.service <<EOF
[Service]
ExecStart=/bin/sleep infinity
EOF
systemctl restart testsuite-23-no-reload.target
systemctl is-active testsuite-23-no-reload.service