On 28/01/12 18:59, Olav Vitters wrote:
I noticed crond wasn't running, nor enabled to start. Enabled it now,
but are others seeing the same? I'm very sure it used to work after
switching to systemd. Something after I switched to systemd broke it I
think.
Yes - I just realised earlier today that my nightly backups have not
been running - since Jan 9th. !!
After:-
systemctl enable crond.service
systemctl start crond.service
It's now running and survives a reboot.
I think this must have happened around the time that there were many
systemd changes taking place.
The status/settings shown in mcc->system->services are still incorrect
but this is a known issue.
Best to check using :-
systemctl status <servicename>.service