summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2013-February/022746.html
blob: ce21f8ce5dbe0c52d8406826881815e2b62476e1 (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
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
<!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=%3C201302111523.44584.jarillon%40abul.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="022739.html">
   <LINK REL="Next"  HREF="022751.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Why ntpdate still there?</H1>
    <B>Pierre Jarillon</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Why%20ntpdate%20still%20there%3F&In-Reply-To=%3C201302111523.44584.jarillon%40abul.org%3E"
       TITLE="[Mageia-dev] Why ntpdate still there?">jarillon at abul.org
       </A><BR>
    <I>Mon Feb 11 15:23:44 CET 2013</I>
    <P><UL>
        <LI>Previous message: <A HREF="022739.html">[Mageia-dev] Why ntpdate still there?
</A></li>
        <LI>Next message: <A HREF="022751.html">[Mageia-dev] Why ntpdate still there?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#22746">[ date ]</a>
              <a href="thread.html#22746">[ thread ]</a>
              <a href="subject.html#22746">[ subject ]</a>
              <a href="author.html#22746">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Le lundi 11 f&#233;vrier 2013 13:18:23, Colin Guthrie a &#233;crit :
&gt;<i> So ntpdate as a service is just a one-shot thing, it happens once at
</I>&gt;<i> boot to ensure the clocks are properly set and then ntpd takes over for
</I>&gt;<i> the rest of the time that machine stays up.
</I>&gt;<i> 
</I>&gt;<i> As far as I'm aware, there is nothing integrated into crontab regarding
</I>&gt;<i> ntpdate, but please feel free to correct me on that one.
</I>
Yes, this was the old system. I am not an expert in ntp, but I have read 
carefully <A HREF="http://ntp.org">http://ntp.org</A> few years ago and I return on it now and then.
I can miss something... I am not the truth!

On the web site <A HREF="http://www.ntp.org/">http://www.ntp.org/</A>  -&gt;Implementation Documentation
<A HREF="http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html">http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html</A> said:
Disclaimer: The functionality of this program is now available in the ntpd 
program. See the -q command line option in the ntpd - Network Time Protocol 
(NTP) daemon page. After a suitable period of mourning, the ntpdate program is 
to be retired from this distribution

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:

-q
Exit the ntpd just after the first time the clock is set. This behavior mimics 
that of the ntpdate program, which is to be retired. The -g and -x options can 
be used with this option. Note: The kernel time discipline is disabled with 
this option.
-g
Normally, ntpd exits with a message to the system log if the offset exceeds the 
panic threshold, which is 1000 s by default. This option allows the time to be 
set to any value without restriction; however, this can happen only once. If 
the threshold is exceeded after that, ntpd will exit with a message to the 
system log. This option can be used with the -q and -x options. See the tinker 
command for other options.

The same options are set in the man of ntp.

IMO, ntpdate should be replaced with: ntpd -gq
I don't understand why ntpdate is listed as an active daemon in drakxservices.

In /etc/sysconfig/ntpd :
- Mageia 1 : OPTIONS=&quot;-u ntp:ntp -p /var/run/ntpd.pid&quot;
- Mageia 2 : OPTIONS=&quot;-g&quot;
- Mageia 3 : OPTIONS=&quot;-g&quot;

Then it seems that ntpdate is no longer useful since Mageia 2.

-- 
Pierre Jarillon - <A HREF="http://pjarillon.free.fr/">http://pjarillon.free.fr/</A>
Vice-pr&#233;sident de l'ABUL : <A HREF="http://abul.org">http://abul.org</A>
Microsoft is for computers what McDonald is for French gastronomy
</PRE>









































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="022739.html">[Mageia-dev] Why ntpdate still there?
</A></li>
	<LI>Next message: <A HREF="022751.html">[Mageia-dev] Why ntpdate still there?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#22746">[ date ]</a>
              <a href="thread.html#22746">[ thread ]</a>
              <a href="subject.html#22746">[ subject ]</a>
              <a href="author.html#22746">[ 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>