docs: clarify systemd unit placement and sudo requirements per permission#613
Merged
creativeprojects merged 1 commit intocreativeprojects:masterfrom Mar 31, 2026
Conversation
…sion Explain which systemd unit location is used for each schedule-permission value, and make it clear that `user` still requires sudo while `user_logged_on` does not. Add a tip pointing users toward lingering as the path to rootless always-on scheduling.
Owner
|
That's a very nice addition, thank you. |
ef83fe3
into
creativeprojects:master
3 of 4 checks passed
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
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.
Thanks for this nice addition to restic! I started to use resticprofile and wanted to setup a systemd timer. Because I struggled with this part of the docs, I thought I could contribute a minor improvement to them upstream for my future self and other people :)