"Unruh" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > "David L. Mills" <[EMAIL PROTECTED]> writes: [...] >> What you report seems to be common practice in packaged systems - >> include the local clock driver - is unfortunate. I consider that a bad >> practice, but then my engineering principles might not coincide with >> their on-ground reality. > > I agree that it is both unfortunate and incomprehensible.
I don't. In a client, it doesn't _hurt_ as long as nobody asks the client for the time. In a server, it can keep the flock together even while the server drifts. Some people may prefer to be explicitly unsynchronised, but for myself I'm happy to accept that stratum 11 means we don't really know what time it is - but wherever we go, we go there together. The fatal flaw, of course, is that with a single package, client and server will both revert to their _own_ local clock. That defeats the purpose. Groetjes, Maarten Wiltink _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
