Doug Hardie wrote: > > On Jul 19, 2007, at 10:08, [LoN]Kamikaze wrote: > >> As the subject says, on my 6-stable systems ntpd just sits there and does >> nothing. The logs only mention when the daemon gets started or shut >> down. It >> complains when servers are not reachable, but does nothing when they >> are available. >> >> The drift file always contains 0.00. >> >> ntpdate and openntpd both successfully manage to set the time, so I >> suppose >> it's a problem with ntpd. > > Are you on a static IP address? If not, ntpd obtains its IP address > when it starts up and uses it forever. If your IP address changes then > it will not be able to communicate with the upstream ntp servers. It > has to be restarted everytime your IP address changes.
I have a static address. The trouble is it seems to operate fine, only it forgets to change the time when it differs from the time servers too much. Sometimes my clock goes wrong more than 1 second within a day. _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
