[Mageia-dev] Why ntpdate still there?

Colin Guthrie mageia at colin.guthr.ie
Mon Feb 11 14:46:22 CET 2013


'Twas brillig, and Johnny A. Solbu at 11/02/13 12:57 did gyre and gimble:
> On Monday 11. February 2013 12.19, Pierre Jarillon wrote:
>> Use of ntpdate in crontab is a very bad idea because a great number of  users 
>> can make a burst of activity and a saturation of servers.
> 
> Then don't use it in crontab.
> 
>> ntpd is more accurate with few requests and can also setup the clock.
>> ntpd makes requests after a long time. More the clock is adjusted, more it 
>> waits before a new request.
> 
> I have a few setups where running an ntp daemon is undesired, yet I need to periodically manually set the clock.
> I have two laptops which is off most of the time, and when I do use them I don't always have a network connection. So I need to set the clock manually using ntpdate when I do have a connection.
> 
> If it disappears I will miss it, and most likely look for a replacement, if there is one.

I did mean to (but forgot) switch us to use crony by default as it's
better for offline drift compensation and such like.

I'll try and remember for mga4 as it's likely too late for mga3.

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