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
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Why ntpdate still there?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Why%20ntpdate%20still%20there%3F&In-Reply-To=%3C5126A811.2050905%40colin.guthr.ie%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="022751.html">
<LINK REL="Next" HREF="023061.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Why ntpdate still there?</H1>
<B>Colin Guthrie</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Why%20ntpdate%20still%20there%3F&In-Reply-To=%3C5126A811.2050905%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] Why ntpdate still there?">mageia at colin.guthr.ie
</A><BR>
<I>Fri Feb 22 00:04:49 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="022751.html">[Mageia-dev] Why ntpdate still there?
</A></li>
<LI>Next message: <A HREF="023061.html">[Mageia-dev] Why ntpdate still there?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23059">[ date ]</a>
<a href="thread.html#23059">[ thread ]</a>
<a href="subject.html#23059">[ subject ]</a>
<a href="author.html#23059">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and Colin Guthrie at 11/02/13 14:55 did gyre and gimble:
><i> 'Twas brillig, and Pierre Jarillon at 11/02/13 14:23 did gyre and gimble:
</I>>><i> Le lundi 11 février 2013 13:18:23, Colin Guthrie a écrit :
</I>>>><i> So ntpdate as a service is just a one-shot thing, it happens once at
</I>>>><i> boot to ensure the clocks are properly set and then ntpd takes over for
</I>>>><i> the rest of the time that machine stays up.
</I>>>><i>
</I>>>><i> As far as I'm aware, there is nothing integrated into crontab regarding
</I>>>><i> ntpdate, but please feel free to correct me on that one.
</I>>><i>
</I>>><i> Yes, this was the old system. I am not an expert in ntp, but I have read
</I>>><i> carefully <A HREF="http://ntp.org">http://ntp.org</A> few years ago and I return on it now and then.
</I>>><i> I can miss something... I am not the truth!
</I>>><i>
</I>>><i> On the web site <A HREF="http://www.ntp.org/">http://www.ntp.org/</A> ->Implementation Documentation
</I>>><i> <A HREF="http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html">http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html</A> said:
</I>>><i> Disclaimer: The functionality of this program is now available in the ntpd
</I>>><i> program. See the -q command line option in the ntpd - Network Time Protocol
</I>>><i> (NTP) daemon page. After a suitable period of mourning, the ntpdate program is
</I>>><i> to be retired from this distribution
</I>>><i>
</I>>><i> And <A HREF="http://www.eecis.udel.edu/~mills/ntp/html/ntpd.html">http://www.eecis.udel.edu/~mills/ntp/html/ntpd.html</A> and the man tell us:
</I>>><i>
</I>>><i> -q
</I>>><i> Exit the ntpd just after the first time the clock is set. This behavior mimics
</I>>><i> that of the ntpdate program, which is to be retired. The -g and -x options can
</I>>><i> be used with this option. Note: The kernel time discipline is disabled with
</I>>><i> this option.
</I>>><i> -g
</I>>><i> Normally, ntpd exits with a message to the system log if the offset exceeds the
</I>>><i> panic threshold, which is 1000 s by default. This option allows the time to be
</I>>><i> set to any value without restriction; however, this can happen only once. If
</I>>><i> the threshold is exceeded after that, ntpd will exit with a message to the
</I>>><i> system log. This option can be used with the -q and -x options. See the tinker
</I>>><i> command for other options.
</I>>><i>
</I>>><i> The same options are set in the man of ntp.
</I>>><i>
</I>>><i> IMO, ntpdate should be replaced with: ntpd -gq
</I>><i>
</I>><i> Yup that would be fine.
</I>><i>
</I>>><i> I don't understand why ntpdate is listed as an active daemon in drakxservices.
</I>><i>
</I>><i> This is simply because of the fact that drakxservices doesn't really
</I>><i> grok the kind of granularity you want here.
</I>><i>
</I>><i> See the direct output from e.g. "systemctl status ntpdate.service" vs.
</I>><i> "systemctl status ntpd.service" (hint: compare "active (exited)" vs
</I>><i> "active (running)")
</I>><i>
</I>><i> For the former, it's a "oneshot" and as it has been run and it ran
</I>><i> successfully, it's is thus considered "active".
</I>><i>
</I>><i> Really we should teach drakxservices to present that properly: e.g. show
</I>><i> it as "Completed" or something, rather than "Active"
</I>><i>
</I>>><i> In /etc/sysconfig/ntpd :
</I>>><i> - Mageia 1 : OPTIONS="-u ntp:ntp -p /var/run/ntpd.pid"
</I>>><i> - Mageia 2 : OPTIONS="-g"
</I>>><i> - Mageia 3 : OPTIONS="-g"
</I>>><i>
</I>>><i> Then it seems that ntpdate is no longer useful since Mageia 2.
</I>><i>
</I>><i> Yes indeed. It seems the -g option passed there makes the separate
</I>><i> ntpdate service obsolete. It basically gives ntpd a one-chance option to
</I>><i> do a big jump, which is basically what we were achieving with that
</I>><i> double unit setup.
</I>><i>
</I>><i> I'll kill off the ntpdate stuff.
</I>><i>
</I>><i> Many thanks for poking into this :)
</I>
Hmm, actually, I'm not sure the -g argument is sensible to pass to the
daemon process generally. It seems that if it cannot reach a server
(i.e. no networking) then the daemon exits.
Certainly that is what I've seen here.
Also, running ntpd -qg here with a large skew seems to not actually work
here :s
[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at jimmy</A> ~]# systemctl stop ntpd.service
[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at jimmy</A> ~]# date
Thu 21 Feb 18:02:19 GMT 2013
[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at jimmy</A> ~]# date
Thu 21 Feb 18:02:23 GMT 2013
[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at jimmy</A> ~]# ntpd -qg
ntpd: time slew +0.000000s
[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at jimmy</A> ~]# ntpdate pool.ntp.org
21 Feb 23:02:53 ntpdate[7741]: step time server 149.5.113.103 offset
18004.588317 sec
[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at jimmy</A> ~]# ntpd -qg
ntpd: time slew +0.000000s
[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at jimmy</A> ~]# systemctl start ntpd.service
So perhaps we should restore the previous setup?
Col
--
Colin Guthrie
colin(at)mageia.org
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
Day Job:
Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
Open Source:
Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="022751.html">[Mageia-dev] Why ntpdate still there?
</A></li>
<LI>Next message: <A HREF="023061.html">[Mageia-dev] Why ntpdate still there?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23059">[ date ]</a>
<a href="thread.html#23059">[ thread ]</a>
<a href="subject.html#23059">[ subject ]</a>
<a href="author.html#23059">[ 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>
|
