Christian Glombek
b3896afea2
Cover the size derivation and the packing decisions that the integration test cannot reach: its veth MTU exceeds every record TEST-89 publishes, so neither the oversized-record fallback nor the drop of a record beyond the RFC 6762 section 17 ceiling is ever exercised there. The cases pin the two size bounds for both families (including the fallback for an MTU not known yet and the jumbo-frame cap), the split at max_size, the lone oversized record in a fragmented packet, the drop of a record that fits nowhere, the skip of a record that cannot be encoded at all, that answer-item flags reach the wire (a goodbye must keep TTL 0 and its cache-flush bit), and that name compression stays within a packet -- the property the split exists for, since every DNS-SD name shares a suffix and a compression pointer may not cross a packet boundary.
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