Yu Watanabe
b27e324272
I noticed that the use of sed in the `80-systemd-osc-context.sh` was unnecessary, and upon writing a replacement in pure bash and testing it, actually buggy. While in there, I also spotted some other minor things that might be worth doing. Getting rid of fork+exec for doing sed is probably the biggest win, but there are still quite a few subshell invocations (that only do fork, not exec). I haven't measured the overhead of those, but it seems that we could get rid of those as well if we want. Another thing I wonder about is whether we should emit an end= marker on shell exit. There's no guaranteed way of doing it. Just as everything else, we could get killed before getting a chance to do it. But also, unlike PROMPT_COMMANDS, there's no "at_exit" array to hook into. Still, we could ask if there is a 'trap exit' hook installed, and if not, install one ourselves; if the user's bashrc subsequently overrides that, so be it (though .bash_logout would be more appropriate).
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