-
Notifications
You must be signed in to change notification settings - Fork 6
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
[Security.NoUser] seems a bit harsh for user unit files #64
Comments
Currently that's not supported, but I'll take it into consideration for the 2.x planning |
That's fine. Looking forward to version 2.0. Thank you for considering it! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure if my assumptions are correct, but I've always written systemd
user
(as opposed tosystem
) units without a User=foo or DynamicUser=bar. systemd itself doesn't do that for user units, as they're designed to be run by the user that calls them viasystemctl --user
. So I was a bit surprised to notice systemdlint always tags these with [Security.NoUser] as an error, regardless where they are placed on the filesystem:Is there a way to drop this notice for user units? Or at least downgrade it to a warning?
The text was updated successfully, but these errors were encountered: