[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #17614] Clock Slew < 1 sec.

From: anonymous
Subject: [bug #17614] Clock Slew < 1 sec.
Date: Tue, 20 May 2008 14:56:23 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20080404 Firefox/

Follow-up Comment #2, bug #17614 (project make):

make[3]: Warning: File `./libPPC85XXgnuAPPtelcoImmib.a' has modification time
--->>0.03 s<<--- in the future

That's three one *hundredths* of one second. Some systems don't allow NTP to
slew their clock, only step it, and in any case, 30 milliseconds is getting
down into trans-router packet transit times, and NTP-startup time skews.

What's more, the NTP daemon's default step threshold is 128ms, or 0.128
seconds, about 43 times larger than the time skew complained about above.

There has to be a cutoff somewhere, even if it's not 1 second, otherwise why
not use (*timespec_t)x->tv_nsec and complain about a file's timestamp being
.000000001 seconds in the future?

How about 0.15 seconds, to exceed the NTP step threshold by 22 milliseconds?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]