USNO and possibly others have misinterpreted the maining of the
leapseconds last-update field and incorrectly increment it when changing the file even though the leapsecond data has not changed. For instance, if a leapsecond file is obtained from USNO, when it expires it will not be replaced by a newer file from other sources because it has an incorrect later last-update (version). This corrects r304780. PR: 225029 Submitted by: ian MFC after: 3 days
This commit is contained in:
parent
0f1ca2cca2
commit
b55d60aa97
@ -144,9 +144,9 @@ ntpd_fetch_leapfile() {
|
||||
done
|
||||
ntp_ver_no_tmp=$(get_ntp_leapfile_ver $ntp_tmp_leapfile)
|
||||
ntp_expiry_tmp=$(get_ntp_leapfile_expiry $ntp_tmp_leapfile)
|
||||
if [ "$ntp_ver_no_tmp" -gt "$ntp_ver_no_db" -o \
|
||||
"$ntp_ver_no_tmp" -eq "$ntp_ver_no_db" -a \
|
||||
"$ntp_expiry_tmp" -gt "$ntp_expiry_db" ]; then
|
||||
if [ "$ntp_expiry_tmp" -gt "$ntp_expiry_db" -o \
|
||||
"$ntp_expiry_tmp" -eq "$ntp_expiry_db" -a \
|
||||
"$ntp_ver_no_tmp" -gt "$ntp_ver_no_db" ]; then
|
||||
$verbose using $url as $ntp_db_leapfile
|
||||
mv $ntp_tmp_leapfile $ntp_db_leapfile
|
||||
else
|
||||
|
Loading…
Reference in New Issue
Block a user