journald now counts received log messages by priority and by transport in $RUNTIME_DIRECTORY/counters, which it keeps mapped for its whole runtime. The counters hence survive restarts of journald, but are reset on reboot. Messages are counted in each transport right after their priority is known, i.e. before any filtering (LogLevelMax=, LogFilterPatterns=, MaxLevelStore=, Storage=none) or rate limiting is applied. Kernel messages are only counted after the kernel seqnum check, so that messages seen before a restart are not counted twice. journald's own messages are not counted. This introduces a JournalTransport enum for the transports we receive messages on, whose string names match the _TRANSPORT= field.
System and Service Manager
Details
Most documentation is available on systemd's website.
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
