From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-January/011613.html | 95 +++++++++++++++++++++++++++++ 1 file changed, 95 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-January/011613.html (limited to 'zarb-ml/mageia-dev/2012-January/011613.html') diff --git a/zarb-ml/mageia-dev/2012-January/011613.html b/zarb-ml/mageia-dev/2012-January/011613.html new file mode 100644 index 000000000..b2f15818c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/011613.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] crond was not set to start + + + + + + + + + +

[Mageia-dev] crond was not set to start

+ Barry Jackson + zen25000 at zen.co.uk +
+ Sat Jan 28 20:57:25 CET 2012 +

+
+ +
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
+
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1