systemd/units/systemd-exit.service

#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Exit the Container
Documentation=man:systemd.special(7)
DefaultDependencies=no
Requires=shutdown.target umount.target final.target
After=shutdown.target umount.target final.target
SuccessAction=exit-force
license: LGPL-2.1+ -> LGPL-2.1-or-later 2020-11-09 12:23:58 +08:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
Add SPDX license headers to unit files 2017-11-19 00:35:03 +08:00			`#`
containers: systemd exits with non-zero code When a systemd service running in a container exits with a non-zero code, it can be useful to terminate the container immediately and get the exit code back to the host, when systemd-nspawn returns. This was not possible to do. This patch adds the following to make it possible: - Add a read-only "ExitCode" property on PID 1's "Manager" bus object. By default, it is 0 so the behaviour stays the same as previously. - Add a method "SetExitCode" on the same object. The method fails when called on baremetal: it is only allowed in containers or in user session. - Add support in systemctl to call "systemctl exit 42". It reuses the existing code for user session. - Add exit.target and systemd-exit.service to the system instance. - Change main() to actually call systemd-shutdown to exit() with the correct value. - Add verb 'exit' in systemd-shutdown with parameter --exit-code - Update systemctl manpage. I used the following to test it: \| $ sudo rkt --debug --insecure-skip-verify run \ \| --mds-register=false --local docker://busybox \ \| --exec=/bin/chroot -- /proc/1/root \ \| systemctl --force exit 42 \| ... \| Container rkt-895a0cba-5c66-4fa5-831c-e3f8ddc5810d failed with error code 42. \| $ echo $? \| 42 Fixes https://github.com/systemd/systemd/issues/1290 2015-09-18 19:37:34 +08:00			`# This file is part of systemd.`
			`#`
			`# systemd is free software; you can redistribute it and/or modify it`
			`# under the terms of the GNU Lesser General Public License as published by`
			`# the Free Software Foundation; either version 2.1 of the License, or`
			`# (at your option) any later version.`

			`[Unit]`
units: fix Description= of systemd-exit.service This file was probably copied from the --user version, let's use some more appropriate wording for the --system version. 2018-11-16 18:39:27 +08:00			`Description=Exit the Container`
containers: systemd exits with non-zero code When a systemd service running in a container exits with a non-zero code, it can be useful to terminate the container immediately and get the exit code back to the host, when systemd-nspawn returns. This was not possible to do. This patch adds the following to make it possible: - Add a read-only "ExitCode" property on PID 1's "Manager" bus object. By default, it is 0 so the behaviour stays the same as previously. - Add a method "SetExitCode" on the same object. The method fails when called on baremetal: it is only allowed in containers or in user session. - Add support in systemctl to call "systemctl exit 42". It reuses the existing code for user session. - Add exit.target and systemd-exit.service to the system instance. - Change main() to actually call systemd-shutdown to exit() with the correct value. - Add verb 'exit' in systemd-shutdown with parameter --exit-code - Update systemctl manpage. I used the following to test it: \| $ sudo rkt --debug --insecure-skip-verify run \ \| --mds-register=false --local docker://busybox \ \| --exec=/bin/chroot -- /proc/1/root \ \| systemctl --force exit 42 \| ... \| Container rkt-895a0cba-5c66-4fa5-831c-e3f8ddc5810d failed with error code 42. \| $ echo $? \| 42 Fixes https://github.com/systemd/systemd/issues/1290 2015-09-18 19:37:34 +08:00			`Documentation=man:systemd.special(7)`
			`DefaultDependencies=no`
units: add the same ordering deps for systemd-exit.service as for systemd-poweroff.service and friends This stuff runs in containers, and should really behave the same everywhere. 2018-11-16 18:34:47 +08:00			`Requires=shutdown.target umount.target final.target`
			`After=shutdown.target umount.target final.target`
units: use correct command to exit Otherwise we'll end a cyclic loop. 2018-11-16 18:35:59 +08:00			`SuccessAction=exit-force`