diff options
author | Lennart Poettering <lennart@poettering.net> | 2016-10-10 22:07:30 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2016-10-10 22:57:01 +0200 |
commit | 1f0958f640b87175cd547c1e69084cfe54a22e9d (patch) | |
tree | e1a49f2a31920394f951f3d14f0e7e06125faab5 /src/core/socket.c | |
parent | 38107f5a4ad5ab148054910040d5d548a4c7a805 (diff) |
core: when determining whether a process exit status is clean, consider whether it is a command or a daemon
SIGTERM should be considered a clean exit code for daemons (i.e. long-running
processes, as a daemon without SIGTERM handler may be shut down without issues
via SIGTERM still) while it should not be considered a clean exit code for
commands (i.e. short-running processes).
Let's add two different clean checking modes for this, and use the right one at
the appropriate places.
Fixes: #4275
Diffstat (limited to 'src/core/socket.c')
-rw-r--r-- | src/core/socket.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/core/socket.c b/src/core/socket.c index b9032fa5c9..1b4a1b3dc3 100644 --- a/src/core/socket.c +++ b/src/core/socket.c @@ -2743,7 +2743,7 @@ static void socket_sigchld_event(Unit *u, pid_t pid, int code, int status) { s->control_pid = 0; - if (is_clean_exit(code, status, NULL)) + if (is_clean_exit(code, status, EXIT_CLEAN_COMMAND, NULL)) f = SOCKET_SUCCESS; else if (code == CLD_EXITED) f = SOCKET_FAILURE_EXIT_CODE; |