From: peppe <g1pi@xxxxxxxxx> If less than 23 hours have passed since the last calibration, hwclock says "Not adjusting drift factor because it has been less than a day since the last calibration.", but in fact compares to 23 hours, not 24. This was originally reported at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689534 Signed-off-by: Andreas Henriksson <andreas@xxxxxxxx> --- sys-utils/hwclock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sys-utils/hwclock.c b/sys-utils/hwclock.c index 0abf01f..bdac003 100644 --- a/sys-utils/hwclock.c +++ b/sys-utils/hwclock.c @@ -989,7 +989,7 @@ 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 - adjtime_p->last_calib_time) < 23 * 60 * 60) { + } else if ((hclocktime - adjtime_p->last_calib_time) < 24 * 60 * 60) { if (debug) printf(_("Not adjusting drift factor because it has " "been less than a day since the last " -- 2.0.0 -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
