I would like to keep ‘service’ if sane/possible. ‘service’ seems to be an agnostic wrapper that works with sysvinit, upstart and systemd. Using ‘systemctl’ would make the package systemd-only. And would also require loads of package changes. Maybe let’s only change it where needed.
‘service’ seems like a not-too-difficult-to-grasp ™ sh script that is easy to debug.
I would like to keep ‘service’ if sane/possible. ‘service’ seems to be an agnostic wrapper that works with sysvinit, upstart and systemd. Using ‘systemctl’ would make the package systemd-only. And would also require loads of package changes. Maybe let’s only change it where needed.
‘service’ seems like a not-too-difficult-to-grasp ™ sh script that is easy to debug.
I had issues using service. I was using them in qubes-whonix and services were not being enable/disabled properly when there was an alias and both sysinit and systemd files. I can’t recall exactly what was giving me issues, it was either control-port…-python or Tor or both. It was only enabling the sysinitv configurations when using service and not systemd unit files.
I had issues using service. I was using them in qubes-whonix and services were not being enable/disabled properly when there was an alias and both sysinit and systemd files. I can't recall exactly what was giving me issues, it was either control-port..-python or Tor or both. It was only enabling the sysinitv configurations when using service and not systemd unit files.
Probably not an issue with 'service'. Probably it was the "don't use spaces in systemd unit files" issue:
- https://phabricator.whonix.org/T316
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786418
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786421
[hr]
Created a ticket as reminder for this…
check if invocations of ‘service’ by Whonix scripts in Whonix 11 is functional: https://phabricator.whonix.org/T331