custom systemd unit files should always go in /etc, not lib#125
Open
alwaysjolley wants to merge 1 commit intoclaranet:masterfrom
Open
custom systemd unit files should always go in /etc, not lib#125alwaysjolley wants to merge 1 commit intoclaranet:masterfrom
alwaysjolley wants to merge 1 commit intoclaranet:masterfrom
Conversation
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.
Simple fix for systemd unit file management. Systemd best practices are to use
/etc/systemd/systemfor any custom unit files. Unit files in /etc override any existing /lib unit files and prevent package changes from interfering with your custom unit file.