2017-11-18 19:09:20 +03:00
/* SPDX-License-Identifier: LGPL-2.1+ */
2010-08-20 05:26:37 +04:00
2015-06-18 10:00:01 +03:00
# include <signal.h>
2015-11-17 00:09:36 +03:00
# include <stdlib.h>
exit-status: list BSD exit codes too
Let's optionally translate BSD exit codes to error strings too.
My first approach on adding this was to turn ExitStatusLevel into a
bitmask rather than a linear level, with one bit for the various feature
bits. However, the exit code ranges are generally not defined
independently from each other, i.e. our own ones are defined with the
LSB ones in mind, and most sets are defined with the ISO C ones.
Hence, instead I changed the existing hierarchy of MINIMAL, SYSTEMD, LSB
with an alias of FULL == LSB, only slightly by seperating FULL and LSB
into two separate levels, so that there's now:
1. MINIMAL (only EXIT_SUCCESS/EXIT_FAILURE)
2. SYSTEMD (incorporating our own exit codes)
3. LSB (like SYSTEMD but adding in LSB service exit codes)
4. FULL (like FULL but adding BSD exit codes)
Note that across the codebase only FULL, SYSTEMD, and MINIMAL are used,
depending on context, how much we know about the process and whether we
are logging for debugging purposes or not. This means the LSB level
wouldn't really have to be separate, but it appeared careless to me to
fold it into FULL along with the BSD exit codes.
Note that this commit doesn't change much for regular codepaths: the
FULL exit status level is only used during debug logging, as a helper to
the user reading the debug logs.
2018-04-23 20:26:25 +03:00
# include <sysexits.h>
2010-08-20 05:26:37 +04:00
# include "exit-status.h"
2012-08-13 15:58:01 +04:00
# include "macro.h"
2015-11-17 00:09:36 +03:00
# include "set.h"
2010-08-20 05:26:37 +04:00
2016-10-10 21:08:41 +03:00
const char * exit_status_to_string ( int status , ExitStatusLevel level ) {
2010-08-20 05:26:37 +04:00
exit-status: list BSD exit codes too
Let's optionally translate BSD exit codes to error strings too.
My first approach on adding this was to turn ExitStatusLevel into a
bitmask rather than a linear level, with one bit for the various feature
bits. However, the exit code ranges are generally not defined
independently from each other, i.e. our own ones are defined with the
LSB ones in mind, and most sets are defined with the ISO C ones.
Hence, instead I changed the existing hierarchy of MINIMAL, SYSTEMD, LSB
with an alias of FULL == LSB, only slightly by seperating FULL and LSB
into two separate levels, so that there's now:
1. MINIMAL (only EXIT_SUCCESS/EXIT_FAILURE)
2. SYSTEMD (incorporating our own exit codes)
3. LSB (like SYSTEMD but adding in LSB service exit codes)
4. FULL (like FULL but adding BSD exit codes)
Note that across the codebase only FULL, SYSTEMD, and MINIMAL are used,
depending on context, how much we know about the process and whether we
are logging for debugging purposes or not. This means the LSB level
wouldn't really have to be separate, but it appeared careless to me to
fold it into FULL along with the BSD exit codes.
Note that this commit doesn't change much for regular codepaths: the
FULL exit status level is only used during debug logging, as a helper to
the user reading the debug logs.
2018-04-23 20:26:25 +03:00
/* Exit status ranges:
*
* 0 … 1 │ ISO C , EXIT_SUCCESS + EXIT_FAILURE
* 2 … 7 │ LSB exit codes for init scripts
* 8 … 63 │ ( Currently unmapped )
* 64 … 78 │ BSD defined exit codes
* 79 … 199 │ ( Currently unmapped )
* 200 … 241 │ systemd ' s private error codes ( might be extended to 254 in future development )
* 242 … 254 │ ( Currently unmapped , but see above )
* 255 │ ( We should probably stay away from that one , it ' s frequently used by applications to indicate an
* │ exit reason that cannot really be expressed in a single exit status value — such as a propagated
* │ signal or such )
*/
switch ( status ) { /* We always cover the ISO C ones */
2010-08-20 05:26:37 +04:00
case EXIT_SUCCESS :
return " SUCCESS " ;
case EXIT_FAILURE :
return " FAILURE " ;
}
exit-status: list BSD exit codes too
Let's optionally translate BSD exit codes to error strings too.
My first approach on adding this was to turn ExitStatusLevel into a
bitmask rather than a linear level, with one bit for the various feature
bits. However, the exit code ranges are generally not defined
independently from each other, i.e. our own ones are defined with the
LSB ones in mind, and most sets are defined with the ISO C ones.
Hence, instead I changed the existing hierarchy of MINIMAL, SYSTEMD, LSB
with an alias of FULL == LSB, only slightly by seperating FULL and LSB
into two separate levels, so that there's now:
1. MINIMAL (only EXIT_SUCCESS/EXIT_FAILURE)
2. SYSTEMD (incorporating our own exit codes)
3. LSB (like SYSTEMD but adding in LSB service exit codes)
4. FULL (like FULL but adding BSD exit codes)
Note that across the codebase only FULL, SYSTEMD, and MINIMAL are used,
depending on context, how much we know about the process and whether we
are logging for debugging purposes or not. This means the LSB level
wouldn't really have to be separate, but it appeared careless to me to
fold it into FULL along with the BSD exit codes.
Note that this commit doesn't change much for regular codepaths: the
FULL exit status level is only used during debug logging, as a helper to
the user reading the debug logs.
2018-04-23 20:26:25 +03:00
if ( IN_SET ( level , EXIT_STATUS_SYSTEMD , EXIT_STATUS_LSB , EXIT_STATUS_FULL ) ) {
switch ( status ) { /* Optionally we cover our own ones */
2010-08-20 05:26:37 +04:00
case EXIT_CHDIR :
return " CHDIR " ;
case EXIT_NICE :
return " NICE " ;
case EXIT_FDS :
return " FDS " ;
case EXIT_EXEC :
return " EXEC " ;
case EXIT_MEMORY :
return " MEMORY " ;
case EXIT_LIMITS :
return " LIMITS " ;
case EXIT_OOM_ADJUST :
return " OOM_ADJUST " ;
case EXIT_SIGNAL_MASK :
return " SIGNAL_MASK " ;
case EXIT_STDIN :
return " STDIN " ;
case EXIT_STDOUT :
return " STDOUT " ;
case EXIT_CHROOT :
return " CHROOT " ;
case EXIT_IOPRIO :
return " IOPRIO " ;
case EXIT_TIMERSLACK :
return " TIMERSLACK " ;
case EXIT_SECUREBITS :
return " SECUREBITS " ;
case EXIT_SETSCHEDULER :
return " SETSCHEDULER " ;
case EXIT_CPUAFFINITY :
return " CPUAFFINITY " ;
case EXIT_GROUP :
return " GROUP " ;
case EXIT_USER :
return " USER " ;
case EXIT_CAPABILITIES :
return " CAPABILITIES " ;
case EXIT_CGROUP :
return " CGROUP " ;
case EXIT_SETSID :
return " SETSID " ;
case EXIT_CONFIRM :
return " CONFIRM " ;
case EXIT_STDERR :
return " STDERR " ;
case EXIT_PAM :
return " PAM " ;
2011-08-02 07:24:58 +04:00
case EXIT_NETWORK :
return " NETWORK " ;
2011-11-17 03:21:16 +04:00
case EXIT_NAMESPACE :
return " NAMESPACE " ;
2012-07-17 06:17:53 +04:00
case EXIT_NO_NEW_PRIVILEGES :
return " NO_NEW_PRIVILEGES " ;
case EXIT_SECCOMP :
return " SECCOMP " ;
2014-02-06 13:05:16 +04:00
case EXIT_SELINUX_CONTEXT :
return " SELINUX_CONTEXT " ;
2014-02-19 05:15:24 +04:00
case EXIT_PERSONALITY :
return " PERSONALITY " ;
2014-02-20 19:19:44 +04:00
case EXIT_APPARMOR_PROFILE :
return " APPARMOR " ;
2014-02-25 23:37:03 +04:00
case EXIT_ADDRESS_FAMILIES :
return " ADDRESS_FAMILIES " ;
2014-03-03 20:14:07 +04:00
case EXIT_RUNTIME_DIRECTORY :
return " RUNTIME_DIRECTORY " ;
2014-06-05 11:55:53 +04:00
2016-10-10 21:11:21 +03:00
case EXIT_CHOWN :
return " CHOWN " ;
2015-07-23 08:17:03 +03:00
case EXIT_SMACK_PROCESS_LABEL :
return " SMACK_PROCESS_LABEL " ;
2016-12-02 03:54:41 +03:00
case EXIT_KEYRING :
return " KEYRING " ;
core: add {State,Cache,Log,Configuration}Directory= (#6384)
This introduces {State,Cache,Log,Configuration}Directory= those are
similar to RuntimeDirectory=. They create the directories under
/var/lib, /var/cache/, /var/log, or /etc, respectively, with the mode
specified in {State,Cache,Log,Configuration}DirectoryMode=.
This also fixes #6391.
2017-07-18 15:34:52 +03:00
case EXIT_STATE_DIRECTORY :
return " STATE_DIRECTORY " ;
case EXIT_CACHE_DIRECTORY :
return " CACHE_DIRECTORY " ;
case EXIT_LOGS_DIRECTORY :
return " LOGS_DIRECTORY " ;
case EXIT_CONFIGURATION_DIRECTORY :
return " CONFIGURATION_DIRECTORY " ;
2010-08-20 05:26:37 +04:00
}
}
exit-status: list BSD exit codes too
Let's optionally translate BSD exit codes to error strings too.
My first approach on adding this was to turn ExitStatusLevel into a
bitmask rather than a linear level, with one bit for the various feature
bits. However, the exit code ranges are generally not defined
independently from each other, i.e. our own ones are defined with the
LSB ones in mind, and most sets are defined with the ISO C ones.
Hence, instead I changed the existing hierarchy of MINIMAL, SYSTEMD, LSB
with an alias of FULL == LSB, only slightly by seperating FULL and LSB
into two separate levels, so that there's now:
1. MINIMAL (only EXIT_SUCCESS/EXIT_FAILURE)
2. SYSTEMD (incorporating our own exit codes)
3. LSB (like SYSTEMD but adding in LSB service exit codes)
4. FULL (like FULL but adding BSD exit codes)
Note that across the codebase only FULL, SYSTEMD, and MINIMAL are used,
depending on context, how much we know about the process and whether we
are logging for debugging purposes or not. This means the LSB level
wouldn't really have to be separate, but it appeared careless to me to
fold it into FULL along with the BSD exit codes.
Note that this commit doesn't change much for regular codepaths: the
FULL exit status level is only used during debug logging, as a helper to
the user reading the debug logs.
2018-04-23 20:26:25 +03:00
if ( IN_SET ( level , EXIT_STATUS_LSB , EXIT_STATUS_FULL ) ) {
switch ( status ) { /* Optionally we support LSB ones */
2010-08-20 05:26:37 +04:00
case EXIT_INVALIDARGUMENT :
return " INVALIDARGUMENT " ;
case EXIT_NOTIMPLEMENTED :
return " NOTIMPLEMENTED " ;
case EXIT_NOPERMISSION :
return " NOPERMISSION " ;
case EXIT_NOTINSTALLED :
2015-04-19 00:38:13 +03:00
return " NOTINSTALLED " ;
2010-08-20 05:26:37 +04:00
case EXIT_NOTCONFIGURED :
return " NOTCONFIGURED " ;
case EXIT_NOTRUNNING :
return " NOTRUNNING " ;
}
}
exit-status: list BSD exit codes too
Let's optionally translate BSD exit codes to error strings too.
My first approach on adding this was to turn ExitStatusLevel into a
bitmask rather than a linear level, with one bit for the various feature
bits. However, the exit code ranges are generally not defined
independently from each other, i.e. our own ones are defined with the
LSB ones in mind, and most sets are defined with the ISO C ones.
Hence, instead I changed the existing hierarchy of MINIMAL, SYSTEMD, LSB
with an alias of FULL == LSB, only slightly by seperating FULL and LSB
into two separate levels, so that there's now:
1. MINIMAL (only EXIT_SUCCESS/EXIT_FAILURE)
2. SYSTEMD (incorporating our own exit codes)
3. LSB (like SYSTEMD but adding in LSB service exit codes)
4. FULL (like FULL but adding BSD exit codes)
Note that across the codebase only FULL, SYSTEMD, and MINIMAL are used,
depending on context, how much we know about the process and whether we
are logging for debugging purposes or not. This means the LSB level
wouldn't really have to be separate, but it appeared careless to me to
fold it into FULL along with the BSD exit codes.
Note that this commit doesn't change much for regular codepaths: the
FULL exit status level is only used during debug logging, as a helper to
the user reading the debug logs.
2018-04-23 20:26:25 +03:00
if ( level = = EXIT_STATUS_FULL ) {
switch ( status ) { /* Optionally, we support BSD exit statusses */
case EX_USAGE :
return " USAGE " ;
case EX_DATAERR :
return " DATAERR " ;
case EX_NOINPUT :
return " NOINPUT " ;
case EX_NOUSER :
return " NOUSER " ;
case EX_NOHOST :
return " NOHOST " ;
case EX_UNAVAILABLE :
return " UNAVAILABLE " ;
case EX_SOFTWARE :
return " SOFTWARE " ;
case EX_OSERR :
return " OSERR " ;
case EX_OSFILE :
return " OSFILE " ;
case EX_CANTCREAT :
return " CANTCREAT " ;
case EX_IOERR :
return " IOERR " ;
case EX_TEMPFAIL :
return " TEMPFAIL " ;
case EX_PROTOCOL :
return " PROTOCOL " ;
case EX_NOPERM :
return " NOPERM " ;
case EX_CONFIG :
return " CONFIG " ;
}
}
2010-08-20 05:26:37 +04:00
return NULL ;
}
2011-01-20 20:22:03 +03:00
2016-10-10 23:07:30 +03:00
bool is_clean_exit ( int code , int status , ExitClean clean , ExitStatusSet * success_status ) {
2011-01-20 20:22:03 +03:00
if ( code = = CLD_EXITED )
2012-08-13 15:58:01 +04:00
return status = = 0 | |
( success_status & &
2018-03-13 10:32:37 +03:00
set_contains ( success_status - > status , INT_TO_PTR ( status ) ) ) ;
2011-01-20 20:22:03 +03:00
2016-10-10 23:07:30 +03:00
/* If a daemon does not implement handlers for some of the signals that's not considered an unclean shutdown */
2011-01-20 20:22:03 +03:00
if ( code = = CLD_KILLED )
2016-10-10 23:07:30 +03:00
return
( clean = = EXIT_CLEAN_DAEMON & & IN_SET ( status , SIGHUP , SIGINT , SIGTERM , SIGPIPE ) ) | |
2012-08-13 15:58:01 +04:00
( success_status & &
2016-06-02 18:41:48 +03:00
set_contains ( success_status - > signal , INT_TO_PTR ( status ) ) ) ;
2011-01-20 20:22:03 +03:00
return false ;
}
2014-07-03 14:47:40 +04:00
void exit_status_set_free ( ExitStatusSet * x ) {
assert ( x ) ;
2016-06-02 18:41:48 +03:00
x - > status = set_free ( x - > status ) ;
x - > signal = set_free ( x - > signal ) ;
2014-07-03 14:47:40 +04:00
}
2014-07-03 17:50:31 +04:00
bool exit_status_set_is_empty ( ExitStatusSet * x ) {
if ( ! x )
return true ;
return set_isempty ( x - > status ) & & set_isempty ( x - > signal ) ;
}
2015-04-28 19:24:20 +03:00
bool exit_status_set_test ( ExitStatusSet * x , int code , int status ) {
if ( exit_status_set_is_empty ( x ) )
return false ;
if ( code = = CLD_EXITED & & set_contains ( x - > status , INT_TO_PTR ( status ) ) )
return true ;
if ( IN_SET ( code , CLD_KILLED , CLD_DUMPED ) & & set_contains ( x - > signal , INT_TO_PTR ( status ) ) )
return true ;
return false ;
}