Open
Conversation
|
Cool! I also want to use Just a few thoughts:
|
Author
|
I used SKIP_PERMCHECK as I'm using it with USB. I just don't want nut to own the device. I did mess up with the env variable in the git commit - I put it into the wrong branch, but if it's merged, it'll be added with #114. |
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.
When running Nutify rootless, the container user cannot change ownership or permissions for /dev/bus/usb, which can cause the startup permission-fix loop to block service startup. This adds a SKIP_PERMCHECK environment variable to bypass the USB permission update step when the host already manages device permissions (e.g., via udev/systemd), allowing Nutify to start without trying to chown/chmod