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
I've noticed Ubuntu 16.04+ and Debian 8+ is using systemd and running conserver as root. The package is still using SysV init and the path where you put the systemd file doesn't exist (they use /lib/systemd/system) and on those systems, the change would be erased on upgrade (it should go in /etc/systemd/system). On both 16.04 and 18.04, I keep running conserver as non-root using the SysV variant (like on 14.04) and it works fine.
Any reason for the current setup?
The text was updated successfully, but these errors were encountered:
Frankly I never used the module on Debian family so there is no rationale to the choice you're describing. Therefore, please make the changes you like, and I'll happily merge them :-)
Hey!
I've noticed Ubuntu 16.04+ and Debian 8+ is using systemd and running conserver as root. The package is still using SysV init and the path where you put the systemd file doesn't exist (they use
/lib/systemd/system
) and on those systems, the change would be erased on upgrade (it should go in/etc/systemd/system
). On both 16.04 and 18.04, I keep running conserver as non-root using the SysV variant (like on 14.04) and it works fine.Any reason for the current setup?
The text was updated successfully, but these errors were encountered: