https://bugzilla.novell.com/show_bug.cgi?id=856986
https://bugzilla.novell.com/show_bug.cgi?id=856986#c5
--- Comment #5 from Reinhard Speyerer
(In reply to comment #2)
Using systemctl enable atd.service seems to have solved the problem for me:
Unfortunately this causes atd to run after the next reboot bash-4.2# rcatd status atd.service - Execution Queue Daemon Loaded: loaded (/usr/lib/systemd/system/atd.service; enabled) Active: active (running) since Mon 2014-01-06 11:04:03 CET; 7h ago Main PID: 568 (atd) CGroup: /system.slice/atd.service `-568 /usr/sbin/atd -f which is not want I wanted.
The bug is in the fact systemctl does not list atd.service, despite being installed and daemon knows about it.
atd.service is listed by systemctl ... list-unit-files instead of ... list-units The following patch --- /sbin/service.orig 2013-12-17 13:59:52.000000000 +0100 +++ /sbin/service 2014-01-06 18:43:38.919824922 +0100 @@ -58,3 +58,3 @@ fi - if sd_booted && systemctl --full --no-legend --no-pager --type=service --all list-units 2>/dev/null|grep -q "^$rc.service"; then + if sd_booted && systemctl --full --no-legend --no-pager --type=service --all list-unit-files 2>/dev/null|grep -q "^$rc.service"; then return 0 seems to do what I want without introducing unwanted side-effects (so far). Regards, Reinhard -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.