-
Notifications
You must be signed in to change notification settings - Fork 880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplify systemd service files #5830
Merged
Merged
Conversation
This file contains 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
TheRealFalcon
approved these changes
Oct 18, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
- RHEL family distros use ds-identify, and therefore the run directory is already made and ds-identify will have created the enabled file. - network.service doesn't appear to ever have been used, and was probably intended to be network.target.
This service is also Before=network-pre.target. NetworkManager.service is ordered After=network-pre.target Therefore, this setting is redundant.
This is required by all distros which use DefaultDependencies=no. It implicitly added by all distros which do not use DefaultDependencies=no. Therefore, it does no harm to apply it in all cases.
- There is no harm in ordering after a service which doesn't exist. - Cloud-init's final stage should consistently be ordered with respect to multi-user.target on all distros.
holmanb
force-pushed
the
holmanb/systemd-cleanup
branch
from
October 18, 2024 20:50
2b9c509
to
aba3f71
Compare
holmanb
added a commit
that referenced
this pull request
Oct 18, 2024
- RHEL family distros use ds-identify, and therefore the run directory is already made and ds-identify will have created the enabled file. - network.service doesn't appear to ever have been used, and was probably intended to be network.target.
holmanb
added a commit
that referenced
this pull request
Oct 18, 2024
This service is also Before=network-pre.target. NetworkManager.service is ordered After=network-pre.target Therefore, this setting is redundant.
holmanb
added a commit
that referenced
this pull request
Oct 18, 2024
This is required by all distros which use DefaultDependencies=no. It implicitly added by all distros which do not use DefaultDependencies=no. Therefore, it does no harm to apply it in all cases.
holmanb
added a commit
that referenced
this pull request
Oct 18, 2024
- There is no harm in ordering after a service which doesn't exist. - Cloud-init's final stage should consistently be ordered with respect to multi-user.target on all distros.
holmanb
added a commit
to holmanb/cloud-init
that referenced
this pull request
Oct 22, 2024
- RHEL family distros use ds-identify, and therefore the run directory is already made and ds-identify will have created the enabled file. - network.service doesn't appear to ever have been used, and was probably intended to be network.target.
holmanb
added a commit
to holmanb/cloud-init
that referenced
this pull request
Oct 22, 2024
This service is also Before=network-pre.target. NetworkManager.service is ordered After=network-pre.target Therefore, this setting is redundant.
holmanb
added a commit
to holmanb/cloud-init
that referenced
this pull request
Oct 22, 2024
This is required by all distros which use DefaultDependencies=no. It implicitly added by all distros which do not use DefaultDependencies=no. Therefore, it does no harm to apply it in all cases.
holmanb
added a commit
to holmanb/cloud-init
that referenced
this pull request
Oct 22, 2024
- There is no harm in ordering after a service which doesn't exist. - Cloud-init's final stage should consistently be ordered with respect to multi-user.target on all distros.
holmanb
added a commit
to holmanb/cloud-init
that referenced
this pull request
Oct 22, 2024
netcho
pushed a commit
to storpool/cloud-init
that referenced
this pull request
Oct 24, 2024
- RHEL family distros use ds-identify, and therefore the run directory is already made and ds-identify will have created the enabled file. - network.service doesn't appear to ever have been used, and was probably intended to be network.target.
netcho
pushed a commit
to storpool/cloud-init
that referenced
this pull request
Oct 24, 2024
This service is also Before=network-pre.target. NetworkManager.service is ordered After=network-pre.target Therefore, this setting is redundant.
netcho
pushed a commit
to storpool/cloud-init
that referenced
this pull request
Oct 24, 2024
This is required by all distros which use DefaultDependencies=no. It implicitly added by all distros which do not use DefaultDependencies=no. Therefore, it does no harm to apply it in all cases.
netcho
pushed a commit
to storpool/cloud-init
that referenced
this pull request
Oct 24, 2024
- There is no harm in ordering after a service which doesn't exist. - Cloud-init's final stage should consistently be ordered with respect to multi-user.target on all distros.
netcho
pushed a commit
to storpool/cloud-init
that referenced
this pull request
Oct 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Additional Context
#5818
Merge type