elysia090
87b81528a8
resolved watches networkd state changes and RTNL updates separately. RTNL is currently processed at SD_EVENT_PRIORITY_IMPORTANT, while networkd state changes are processed later at SD_EVENT_PRIORITY_IMPORTANT+5. If both are pending, an RTM_NEWADDR update can make a link relevant for LLMNR/mDNS scope allocation before resolved has consumed the corresponding networkd state update. This can let scope recalculation use stale per-link settings until the networkd event is processed. Run the networkd monitor source before RTNL by using SD_EVENT_PRIORITY_IMPORTANT-5. This lets resolved consume current link settings before reacting to RTNL address updates in the same event loop iteration. Fixes #42079 Co-developed-by: OpenAI Codex <noreply@openai.com>
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