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 <elseifthen@gmx.com>
This commit is contained in:
parent
66af1c0f44
commit
bbb4c273e9
|
@ -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) {
|
||||
/*
|
||||
|
|
Loading…
Reference in New Issue