[wellylug] NTP

[andrej at paradise.net.nz]

Quoting David Antliff <david.antliff at gmail.com>:

> 
> On Fri, 16 Dec 2005 andrej at paradise.net.nz wrote:
> > Heh .. well, since ntpdate is on the list of the
> > "soon to be deprecated" systems I wouldn't want my
> > distro of choice to use it by default :}
> 
> I'm not familiar with that list. Is it a Gentoo Org list? Does it
> indicate 
> what will replace it? Will ntpd be extended to cope with larger 
> differences? Perhaps it has been already? Or is the package being 
> deprecated in whatever distro you choose to use but ntpdate is just
> being moved to the ntpd package?
It has NOTHING to do with Gentoo ... it's from the
maintainer of ntp

> 
> If there's no other better solution yet, then what's wrong with using
> it? 
> It works, doesn't it?
links /usr/doc/ntp-4.2.0/html/ntpd.html
   In some cases it may not be practical for ntpd to run continuously. A        
   common workaround has been to run the ntpdate program from a cron job at     
   designated times. However, this program does not have the crafted signal     
   processing, error checking and mitigation algorithms of ntpd. The -q         
   option is intended for this purpose. Setting this option will cause ntpd     
   to exit just after setting the clock for the first time. The procedure for   
   initially setting the clock is the same as in continuous mode; most          
   applications will probably want to specify the iburst keyword with the       
   server configuration command. With this keyword a volley of messages are     
   exchanged to groom the data and the clock is set in about 10 s. If nothing   
   is heard after a couple of minutes, the daemon times out and exits. After    
   a suitable period of mourning, the ntpdate program may be retired.           


> -- 
> David.
Cheers,
Andrej