* Transport clock skews:
- Store and report UDP clock skews even for large values, so a badly skewed local clock will be reported to the console - Don't shitlist for NTCP clock skew if we don't know what time it is - If NTP hasn't worked yet, have NTCP or SSU update the clock one time - Include failed clock skew in NTCP skew vector if there aren't many connections - Don't include NTCP clock skews for non-established connections - Fix framed clock skew frame size - Report framed clock skew even if for only one peer, if NTP hasn't worked yet - Don't log RRD errors after clock adjustment - Reduce min skew for console warning to 30s (was 45s) - More Java 5 cleanups
This commit is contained in:
@ -92,9 +92,10 @@ public class Clock implements Timestamper.UpdateListener {
|
||||
else if (getLog().shouldLog(Log.INFO))
|
||||
getLog().info("Updating clock offset to " + offsetMs + "ms from " + _offset + "ms");
|
||||
|
||||
if (!_statCreated)
|
||||
if (!_statCreated) {
|
||||
_context.statManager().createRateStat("clock.skew", "How far is the already adjusted clock being skewed?", "Clock", new long[] { 10*60*1000, 3*60*60*1000, 24*60*60*60 });
|
||||
_statCreated = true;
|
||||
}
|
||||
_context.statManager().addRateData("clock.skew", delta, 0);
|
||||
} else {
|
||||
getLog().log(Log.INFO, "Initializing clock offset to " + offsetMs + "ms from " + _offset + "ms");
|
||||
|
Reference in New Issue
Block a user