On Sat, 2005-05-14 at 02:25 -0400, Marty wrote: > I don't want to argue if you are happy, but it doesn't sound fixed > to me. NTP should keep your clock on time to within a few miliseconds. > If you notice any abrupt changes that means NTP is definitely not > working.
That's what I was trying to say. There's no mechanism I know of where booting a bsd disk would fix the clock. But it's *is* working. Still today. NTP is doing its job exactly as expected -- the peers and associations lists in ntpq look like they should. But NTP won't correct time if it's too far off when the server starts. And yesterday, I could bring the time within the window with ntpdate, but after the server got going, the time was far enough off that NTP wanted nothing to do with it. The only thing I can think of is that something got bent in the power failure -- something that the Debian boot process doesn't look at and set, but BSD does. But I don't quite believe it, and I have no suspects for the "something." -- Glenn English [EMAIL PROTECTED] GPG ID: D0D7FF20
signature.asc
Description: This is a digitally signed message part
