In article <[EMAIL PROTECTED]>, Maarten Wiltink <[EMAIL PROTECTED]> wrote:0
> That particular problem is caused by having a number of peers all at > the same local-clock stratum. If one of them is put at a lower stratum Isn't the real problem caused by the use of the local clock driver. Distributors like including this and users don't understand that ntpd will maintain frequency even without any servers, so a lot of people include them without really understanding them. The other problem is that many people think that ntpd is designed to negotiate a consensus time under such circumstances, when except possibly for the new isolated networks option, it isn't and one should use timed, or similar, instead. _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
