on Mon, Sep 24, 2001 at 07:04:05PM -0400, Doug Fields ([EMAIL PROTECTED]) wrote: > > > > I then restart the ntp daemon and noticed my date never changed. > > > However, earlier, I used ntpdate to sync with that time server > > > and it worked. (I make sure both aren't running at the same time) > > > >Have you tried running ntp recently? Often the time difference is too > >great for ntp to sync initially. After you run ntpdate and sync up with > >the time server then ntp can do it's work. > > Definitely do this, yes. But also realize that NTP does not do a sudden > date change. It merely slows down or speeds up the system clock a tiny > fraction for long enough to "drift" your clock into synchronization. > NTPDate, however, does the brute force slam dunk "it says it's 12:34, so > your clock is now 12:34" type of setting.
...which isn't a bad thing to do at startup -- there's not much on your system that's gotten too comfortable with the notion that now is now and not then. So you generally want to run ntpdate at startup (shortly after networking is enabled) to force your system to the proper time. After which, you run ntpd to keep the time accurate. Peace. -- Karsten M. Self <kmself@ix.netcom.com> http://kmself.home.netcom.com/ What part of "Gestalt" don't you understand? Home of the brave http://gestalt-system.sourceforge.net/ Land of the free Free Dmitry! Boycott Adobe! Repeal the DMCA! http://www.freesklyarov.org Geek for Hire http://kmself.home.netcom.com/resume.html
pgp5vqEFPtuEe.pgp
Description: PGP signature
