Since the update from mga1 to mga2-beta3, my scheduled tasks aren't running. crond doesn't appears in "ps" command. crond is present in the directory /etc/rc.d/init.d/ If I launch crond manually, it is ok for the scheduled tasks. But after a reboot, crond is not running again, and it's not ok for the scheduled tasks. >systemctl status crond.service crond.service - Command Scheduler Loaded: loaded (/lib/systemd/system/crond.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/crond.service The last entry of :/var/log/cron/info.log is from before the update to beta3. There is already something about that in the bug : https://bugs.mageia.org/show_bug.cgi?id=4145 marked as resolved and concerning alpha3, that's the reason why I re-post a new bug.
CC: (none) => dmorganec, mageiaBlocks: (none) => 3342
I believe this happens because rpm-helper was updated after crond. Can you confirm by checking the installation date/time of the two packages: rpm -qi cronie rpm -qi rpm-helper We've discussed this on the list and we'll need a solution for the final release, but if you could confirm the theory, that would be great.
Oh and to enable it, just type "systemctl enable crond.service" and it should be started next boot (but obviously we need to solve the transition problem)
Hi, you where right : Name : cronie Version : 1.4.8 Release : 2.mga2 Architecture: x86_64 Install Date: jeu. 19 avril 2012 12:59:29 CEST Name : rpm-helper Version : 0.24.8 Release : 1.mga2 Architecture: noarch Install Date: jeu. 19 avril 2012 14:56:55 CEST and "systemctl enable crond.service" made crond starting after reboot. Just to mention that in mcc/system/manage system services by (dis)enabling the "at startup" box was checked... And now its status is "stopped" (despite that it is running!)
Yeah the MMC services stuff still needs to be converted over for systemd support.. it's on my list. Glad this is a known issue, even if there is not a tracking bug for it yet. I've opened one now bug #5556. Thanks for the report. *** This bug has been marked as a duplicate of bug 5556 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE