From 3a89cb84a62314c3c4807016dbff4359d6988d79 Mon Sep 17 00:00:00 2001 From: Daan De Meyer Date: Tue, 11 Apr 2023 13:17:13 +0200 Subject: core: Propagate exit status via notify socket when running in VM When running in a container, we can propagate the exit status of pid1 as usual via the process exit status. This is not possible when running in a VM. Instead, let's send EXIT_STATUS=%i via the notify socket if one is configured. The user running the VM can then pick up the exit status from the notify socket after the VM has shut down. --- src/shutdown/shutdown.c | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'src/shutdown/shutdown.c') diff --git a/src/shutdown/shutdown.c b/src/shutdown/shutdown.c index a8248901ce..b1dac20c69 100644 --- a/src/shutdown/shutdown.c +++ b/src/shutdown/shutdown.c @@ -14,6 +14,8 @@ #include #include +#include "sd-daemon.h" + #include "alloc-util.h" #include "async.h" #include "binfmt-util.h" @@ -570,6 +572,10 @@ int main(int argc, char *argv[]) { if (!in_container) sync_with_progress(); + /* This is primarily useful when running systemd in a VM, as it provides the user running the VM with + * a mechanism to pick up systemd's exit status in the VM. */ + (void) sd_notifyf(0, "EXIT_STATUS=%i", arg_exit_code); + if (streq(arg_verb, "exit")) { if (in_container) { log_info("Exiting container."); -- cgit v1.2.1