Allison Karlitskaya
516df12af9
If you're using `udevadm monitor` from a script, without a tty, then libc defaults to being fully-buffered, and won't flush stdout after newlines. This is fine for tools that dump a bunch of data and then exit immediately. It's a problem for tools like `udevadm monitor` which have long pauses: the buffered data can get stuck in the buffer for an unbounded amount of time. In the Cockpit project we've been working around this for some time with `stdbuf` which is a `LD_PRELOAD` hack to change the libc buffering behaviour, but we'd like to stop doing that. Let's make sure we flush the buffer after each event.
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