As stated in the man page,
systemctl --now enable servicename
should enable and start the service.
But it never works for me, under many different distributions.
While the output of:
systemctl is-enabled turns enabled,
systemctl is-active is still inactive for the service.
What this switch is good for?
I've tried other combinations such as:
systemctl enable --now servicename
systemctl enable servicename --now
but still the same; I have to manually
systemctl start servicename every time, even if the previous command (ie the
enable part) executes successfully.
Is it that the application's implentation of systemd service should support it implementing the feature somewhere in the unit files; what many well-known services do not follow, that made me think its entirely useless switch; I assume thinking over it.