David L. Mills wrote: > David, > > The bit is never set, so the system calls never show error.
That conflicts with the evidence presented by the questioner. I think it is true that ntpd never sets it in the kernel(although 4.2.4p4 (which is more recent than his) does set it in the user space copy. However the kernel does set it, as I already noted, on startup, when the time is set manually, and when the estimated error hits its end stop. However, that is largely irrelevant, as one could rephrase the question to be, earlier versions of ntpd used to set the estimated error to soem low value when started, why is his version leaving it set at 16+ seconds? (I suspect user error.) > David Woolley wrote: >> David L. Mills wrote: >> >>> >>> It doesn't make sense to manage that bit. Use the maximum error >>> statistic instead. >> >> >> Whilst that is a good suggestion. Those statistics are also showing >> an alarm state in this case. _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
