Chris Lindee
b88ab1c2dd
Bash does not provide an easy way to discern if an exit status came from a signal, or was a legitimate non-zero exit (i.e. a failure). It can be done, by using job control or by invoking another program; however, such approaches require modifying the command entered by a user and are, thus, invasive and risky. Since an exit status of 129 on a command could either indicate it exited cleanly with `exit(129)` or was interrupted by `SIGHUP`, the osc context should report both possibilities, to acknowledge our uncertainty. Given we have no idea what happened, besides an unsuccessful exit, the exit is described as `exit=failure`. Moreover, discerning between an `interrupt` and a `crash` with a command likely involves categorizing every signal. It is fairly obvious `SIGINT` is an interrupt and also obvious, IMO, that `SIGSEGV` is a crash. Avoid the complication (and potential disagreements) by using the encompassing, generic value — one that remains true if no signal occurred. References: [0] https://stackoverflow.com/a/66431355
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release