Skip to content

docs: clarify systemd unit placement and sudo requirements per permission#613

Merged
creativeprojects merged 1 commit intocreativeprojects:masterfrom
fgrosse:docs/clarify-systemd-user-permission
Mar 31, 2026
Merged

docs: clarify systemd unit placement and sudo requirements per permission#613
creativeprojects merged 1 commit intocreativeprojects:masterfrom
fgrosse:docs/clarify-systemd-user-permission

Conversation

@fgrosse
Copy link
Copy Markdown
Contributor

@fgrosse fgrosse commented Mar 29, 2026

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 :)

…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.
@creativeprojects
Copy link
Copy Markdown
Owner

That's a very nice addition, thank you.
The documentation deserves some love, but we're working on it 😆

@creativeprojects creativeprojects merged commit ef83fe3 into creativeprojects:master Mar 31, 2026
3 of 4 checks passed
@creativeprojects creativeprojects added this to the v0.33.0 milestone Apr 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants