You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
@phaus Thanks for the suggestion. However my concern is not how to start the service as root (for which the sudo solution works fine!), it's rather that I do not want to have the service running 24/7 with root privileges. Network services should ideally be owned and run by an unprivileged user.
Normally a process that requires root for some reason starts out with root, does its' thing (such as binding a port), then drops the root privileges and continues executing with some arbitrary user, such as www-data in the case of nginx or apache.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the tool requires root to run (on Linux and macOS, not FreeBSD & SmartOS) because
zpool
which it wraps requires root.It's generally not recommended to run network services as root. Two ideas that I've been thinking about:
The text was updated successfully, but these errors were encountered: