|
From: | Eric Reischer |
Subject: | High-Precision NFS Timestamps |
Date: | Wed, 12 Jan 2011 17:08:26 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101226 Iceowl/1.0b1 Icedove/3.0.11 |
make: *** Warning: .LOW_RESOLUTION_TIME file .lib_deps has a high resolution time stamp
make: warning: Clock skew detected. Your build may be incomplete.Since asking to have system clocks of NFS clients and servers synced to sub-millisecond precision is a bit excessive, is there a way (or feature request: could there be a way) to set the threshold for clock skews either via a runtime Makefile directive, or an environment variable? I can't see any other way to eliminate these warnings without reverting back to ext3 (which isn't happening). If it's a hard-coded value, there should be at least a little room for slop in there (~5 milliseconds?) due to network lag, etc. Even on a point-to-point network, there's going to be one-way transit times of a millisecond or two.
Cheers
[Prev in Thread] | Current Thread | [Next in Thread] |