253052686c
When something goes awry, we would get identical log messages from all the bpf subsystems. E.g. "Failed to load BPF object: %m" appeared 5 times in the sources. But it is very important to know *which* object we failed to load. This could be guessed, e.g. from surroudning messages or from filename/line metadata, but when we get log messages in bug reports, this might not be available. Let's make the messages distinguishable. While at it, some messages were adjusted a bit. In particular, we shouldn't use internal names like BPFProgram which have no meaning outside of the codebase. (cherry picked from commit b1acbc08e29cf92ebff3d3e726474c9d642f6d32)
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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.