You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running su-exec with wrong parameters, you get the Usage: [...] text, but the exit status code is zero (0) which hides the problem on systems relying on status codes signals, e.g. CI environments or shell scripts using set -e
- If su-exec is used as part of an environment where exit codes are
used to signal errors. We can consider using wrong number of
arguments as an error, then we can use exit(1) for that.
Based on a review by @michaelbaudino
> According to /usr/include/sysexits.h (Linux) / man 3 sysexits
> (*BSD), shouldn't we return 64 (EX_USAGE) here, to comply with POSIX
> standard?
When running
su-exec
with wrong parameters, you get theUsage: [...]
text, but the exit status code is zero (0
) which hides the problem on systems relying on status codes signals, e.g. CI environments or shell scripts usingset -e
The text was updated successfully, but these errors were encountered: