blob: b2f15818c7527ce7760eb40c3dca96a1c844b402 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] crond was not set to start
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20crond%20was%20not%20set%20to%20start&In-Reply-To=%3C4F245325.6010301%40zen.co.uk%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="011612.html">
<LINK REL="Next" HREF="011615.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] crond was not set to start</H1>
<B>Barry Jackson</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20crond%20was%20not%20set%20to%20start&In-Reply-To=%3C4F245325.6010301%40zen.co.uk%3E"
TITLE="[Mageia-dev] crond was not set to start">zen25000 at zen.co.uk
</A><BR>
<I>Sat Jan 28 20:57:25 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="011612.html">[Mageia-dev] crond was not set to start
</A></li>
<LI>Next message: <A HREF="011615.html">[Mageia-dev] crond was not set to start
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11613">[ date ]</a>
<a href="thread.html#11613">[ thread ]</a>
<a href="subject.html#11613">[ subject ]</a>
<a href="author.html#11613">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 28/01/12 18:59, Olav Vitters wrote:
><i> I noticed crond wasn't running, nor enabled to start. Enabled it now,
</I>><i> but are others seeing the same? I'm very sure it used to work after
</I>><i> switching to systemd. Something after I switched to systemd broke it I
</I>><i> think.
</I>><i>
</I>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
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="011612.html">[Mageia-dev] crond was not set to start
</A></li>
<LI>Next message: <A HREF="011615.html">[Mageia-dev] crond was not set to start
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11613">[ date ]</a>
<a href="thread.html#11613">[ thread ]</a>
<a href="subject.html#11613">[ subject ]</a>
<a href="author.html#11613">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|