On Tue, Apr 15, 2014 at 09:18:35PM +0400, Andrey Borzenkov wrote:
В Tue, 15 Apr 2014 12:16:20 +0200
Ralf Haferkamp <rhafer(a)suse.de> пишет:
with systemd we nowadays handle enabling services by default via the
systemd-preset-* packages. But AFAICS this really only handles automatic
enablement of the service (== systemctl enable). The service are still not
running after that. For that I still need to either reboot a call systemctl
start manually. Is that really the expected behavior?
Was it different with sysvinit? I.e. is it regression?
At least when comparing cronjobs to systemd timers it is: For a
cronjob you simply place the script e.g. in /etc/cron.daily. For
systemd you need the 1. script, the 2. service file, 3. the timer
file, 4. extend presets, add 5. rpm macros to the spec file and
still 6. reboot or start the service.
For me the solution was easy: Keep the cronjob.
Arvin Schnell, <aschnell(a)suse.de>
Senior Software Engineer, Research & Development
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org