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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While using
$USERis an improvement over a hardcoded username, it's better practice and more robust to use systemd's own specifiers in unit files. The$USERvariable might not always be set in all environments where the service could run, whereas systemd specifiers are guaranteed to be substituted correctly.You can use the
%sspecifier, which expands to the user's configured shell from the user database. This simplifies theExecStartdirective significantly and makes it more efficient by avoiding the need to run/bin/sh,getent, andcutjust to find the user's shell.This is cleaner, more efficient, and less prone to errors.