I had 3 servers and when looking in the logs, saw a lot of connection problems. Also, system was showing problem stopping the ntpd when shutting down or rebooting. If I would check the server it was usually fine from my memory. Also, I think it would depend on if your system keeps time well or not. My system is usually on the money except for a few secs or so. I have ntpd setup on my Dad's system cause his time is off a lot. I haven't heard any complaint from him though, like I had.
Have also seen a lot of people recommending ntpdate over ntpd. Maybe they had the same problem or it's just another urban myth. :) > > What do you mean with 'ntpdate works better'? > > I'm using ntpd here for over 5 years with a lot of success. > The main difference between ntpdate and ntpd is that ntpdate sets the > time once in a (possibly) huge jump and exits, whereas ntpd slowly ties > the local clock to the exteren reference clock. > Ntpdate is good to be run once - at boot time. Then don't run it again > or your sytem time may jump - which some daemons really don't like - > especially if the time jumps backwards. > Ntpd should be started with at least three external reference servers > and asures that your local clock is as much in sync with those servers > as possible. > > Cheers, > Juri -- [EMAIL PROTECTED] mailing list
