[Cerowrt-devel] cerowrt 3.3.8-17: nice latency improvements, some issues with bind

George Lambert marchon at gmail.com
Mon Aug 20 17:27:07 EDT 2012

Good point - that is just how I do it on my server network, sorry.

reminds me of a good point

Q: what is the different between in theory and in practice?
A: In theory, NOTHING.

;-) so we test and iterate until we get it right in practice.


On Mon, Aug 20, 2012 at 4:48 PM, <david at lang.hm> wrote:

> On Mon, 20 Aug 2012, George Lambert wrote:
>  Check and set the time by syncing to NTP Servers - not user supplied times
>> if the network
>> is available. to see if they have set times > those set by NTP Server
> In theory you are right, in practice you are not.
> it's not uncommon for systems to point at a local set of timeservers (GPS
> based for example), sometimes things go wrong with those servers, and so
> people configure a local fallback (because they need the clocks on the
> systems to remain consistant for things like kerberos to keep working).
> This leads to a failure mode where if something goes wrong on that system,
> the time can get set via NTP to some time in the future.
> There needs to be a way to recover from such conditions.
> The recent problems that people had with leap seconds is an indication
> that even if you do use Internet NTP servers, sometimes things go wrong.
> David Lang

P THINK BEFORE PRINTING: is it really necessary?

This e-mail and its attachments are confidential and solely for the
intended addressee(s). Do not share or use them without approval. If
received in error, contact the sender
and delete them.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/cerowrt-devel/attachments/20120820/3910c609/attachment-0002.html>

More information about the Cerowrt-devel mailing list