From: J William Piggott Date: Mon, 20 Oct 2014 19:22:24 +0000 (-0400) Subject: hwclock: Reduce drift factor update period X-Git-Tag: v2.26-rc1~289 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bbb4c273e9b97268ed07520a203d887a2cb15044;p=thirdparty%2Futil-linux.git hwclock: Reduce drift factor update period To facilitate the calculation of 'cold' vs 'warm' Hardware Clock drift factor the limit on the update period needs to be less than 8 hours. 4 hours should be enough drift to allow calculations that are not grossly out of range. For example, with a workstation that is shutdown every night the cold drift factor can be significantly different than a drift factor based on a 24 hour period. Signed-off-by: J William Piggott --- diff --git a/sys-utils/hwclock.c b/sys-utils/hwclock.c index b7fbb98e9b..008b20abed 100644 --- a/sys-utils/hwclock.c +++ b/sys-utils/hwclock.c @@ -1015,10 +1015,10 @@ adjust_drift_factor(struct adjtime *adjtime_p, "calibration time is zero,\n" "so history is bad and calibration startover " "is necessary.\n")); - } else if ((hclocktime.tv_sec - adjtime_p->last_calib_time) < 24 * 60 * 60) { + } else if ((hclocktime.tv_sec - adjtime_p->last_calib_time) < 4 * 60 * 60) { if (debug) printf(_("Not adjusting drift factor because it has " - "been less than a day since the last " + "been less than four hours since the last " "calibration.\n")); } else if (adjtime_p->last_calib_time != 0) { /*