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/011616.html | 102 ++++++++++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-January/011616.html (limited to 'zarb-ml/mageia-dev/2012-January/011616.html') diff --git a/zarb-ml/mageia-dev/2012-January/011616.html b/zarb-ml/mageia-dev/2012-January/011616.html new file mode 100644 index 000000000..6264b54e7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/011616.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] crond was not set to start + + + + + + + + + +

[Mageia-dev] crond was not set to start

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Sat Jan 28 22:35:33 CET 2012 +

+
+ +
'Twas brillig, and Anssi Hannula at 28/01/12 20:16 did gyre and gimble:
+> On 28.01.2012 20: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, services get disabled when migrating to systemd. Some others I
+> noticed on my system were ntpd and avahi...
+
+Yeah, but this is something Olav specifically reckons isn't actually the
+problem in his case (FWIW, I was talking to dmorgan about it on Friday.
+I reckon I can fix in the rpm-helper script)
+
+My crond.service was disabled, but I can't specifically remember
+enabling it on this machine, so that doesn't really help much.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + +
+

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