From d13b60d8af64b2c13e858f6573de9debbf5f5f16 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Iago=20L=C3=B3pez=20Galeiras?= Date: Fri, 11 Dec 2020 13:24:13 +0100 Subject: [PATCH] exit-status: add EXIT_BPF It will be used later. --- src/shared/exit-status.c | 5 +++-- src/shared/exit-status.h | 1 + 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/src/shared/exit-status.c b/src/shared/exit-status.c index db978fb8969..9063f231e15 100644 --- a/src/shared/exit-status.c +++ b/src/shared/exit-status.c @@ -18,8 +18,8 @@ const ExitStatusMapping exit_status_mappings[256] = { * 8…63 │ (Currently unmapped) * 64…78 │ BSD defined exit codes * 79…199 │ (Currently unmapped) - * 200…243 │ systemd's private error codes (might be extended to 254 in future development) - * 244…254 │ (Currently unmapped, but see above) + * 200…244 │ systemd's private error codes (might be extended to 254 in future development) + * 245…254 │ (Currently unmapped, but see above) * * 255 │ EXIT_EXCEPTION (We use this to propagate exit-by-signal events. It's frequently used by others apps (like bash) * │ to indicate exit reason that cannot really be expressed in a single exit status value — such as a propagated @@ -71,6 +71,7 @@ const ExitStatusMapping exit_status_mappings[256] = { [EXIT_CONFIGURATION_DIRECTORY] = { "CONFIGURATION_DIRECTORY", EXIT_STATUS_SYSTEMD }, [EXIT_NUMA_POLICY] = { "NUMA_POLICY", EXIT_STATUS_SYSTEMD }, [EXIT_CREDENTIALS] = { "CREDENTIALS", EXIT_STATUS_SYSTEMD }, + [EXIT_BPF] = { "BPF", EXIT_STATUS_SYSTEMD }, [EXIT_EXCEPTION] = { "EXCEPTION", EXIT_STATUS_SYSTEMD }, diff --git a/src/shared/exit-status.h b/src/shared/exit-status.h index 05707bf722d..3f9a2ad54fb 100644 --- a/src/shared/exit-status.h +++ b/src/shared/exit-status.h @@ -71,6 +71,7 @@ enum { EXIT_CONFIGURATION_DIRECTORY, EXIT_NUMA_POLICY, EXIT_CREDENTIALS, + EXIT_BPF, EXIT_EXCEPTION = 255, /* Whenever we want to propagate an abnormal/signal exit, in line with bash */ }; -- 2.47.3