nfsd.service: Do not require unbound.service #192
Merged
+2
−1
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
pmenzel
approved these changes
Jun 2, 2021
We do require host name resolution on startup (otherwise the exports won't work). However, a "Requires"-dependency on unbound.service is too strong, because we don't want to restart nfsd when unbound ist restarted. Reduce it to a "Wants" dependency.
donald
force-pushed
the
fix-unbound-dependency
branch
from
0ab0c09
to
4d51488
Compare
Sign in
to join this conversation on GitHub.
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.
We do require host name resolution on startup (otherwise the exports
won't work). However, a "Requires"-dependency on unbound.service is too
strong, because we don't want to restart nfsd when unbound ist
restarted. Reduce it to a "Wants" dependency.