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. It seems what ntpd has in complexity it lacks in robustness. I'd prefer to have openntpd in the base system. It seems to be very simple. And it works. _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
