Open richard-mauri opened 3 years ago
My service manager journalctl is full of chown permission errors. The linux process is running as root user and directory and files are all owned by root. I see no reason for chowning alal the time. I resorted to forking the repo and using the no-op chown always.
I think the chown should be configurable to enable/disable as needed.
Why is it always done
I agree with you
My service manager journalctl is full of chown permission errors. The linux process is running as root user and directory and files are all owned by root. I see no reason for chowning alal the time. I resorted to forking the repo and using the no-op chown always.
I think the chown should be configurable to enable/disable as needed.
Why is it always done