I've _never_ seen this behaviour or had users report it; perhaps there's
something unusual about your installs that's making it happen, or about
ours that makes it go away. We're presently using ntpd and running AFS
with -nosettime, as God intended. FWIW, I'm pretty sure that Andrew uses
the time-sync support in AFS on their 4.2-based workstations (as they do
on every other platform), so I'm pretty sure that code works correctly.
I think what Brandon is saying is that he's noticing that his machines
are drifting significantly without running NTP, and that this might be a
problem. Some of the reports of drifts of the order of 10-15
seconds/day can be written off to simply sucky PC hardware, but the
reports of drifts of minutes per minutes can't just be bad hardware.
Esecpailly in Brandon's case, where he's seeing significant drift
*forward* in time.
Sure, running NTP will solve the problem, but the question is whether
there's a real problem that we're just papering over by running NTP.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/