fix(unit): order systemd-resolved after systemd-sysctl - #425
Open
deepin-ci-robot wants to merge 1 commit into
Conversation
Otherwise, IPv6 enable/disable setting may be changed after resolved is started. Changes: - Add debian/patches/fix-unit-order-systemd-resolved-after-systemd-sysctl.patch - Modify debian/patches/series - Modify debian/changelog Upstream: systemd/systemd@6e6b59e Generated-By: glm-5.3-flash Co-Authored-By: deepin-ci-robot <packages@deepin.org>
Contributor
Author
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
TAG Bot TAG: 255.2-4deepin68 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem Before the Change
systemd-resolved.servicewas only ordered aftersystemd-sysusers.service. Without an ordering dependency onsystemd-sysctl.service, sysctl values could be applied after resolved had already started, so the IPv6 enable/disable setting (net.ipv6.conf.default.disable_ipv6etc.) may be changed after resolved is started, leaving resolved with a stale view of IPv6 availability.What This PR Changes
Backports upstream systemd commit 6e6b59ed (PR #30691): adds
systemd-sysctl.serviceto theAfter=line ofunits/systemd-resolved.service.in, so thatsystemd-resolved.serviceis always started after sysctl settings have been applied.Problem Solved After the Change
systemd-resolvednow starts only aftersystemd-sysctl.servicehas run, ensuring IPv6 enable/disable settings are applied before resolved starts, so resolved no longer observes IPv6 settings being changed underneath it.Changes
Upstream
systemd/systemd@6e6b59e
Generated-By: glm-5.3-flash
Co-Authored-By: deepin-ci-robot packages@deepin.org