There is an optional flag to leapsec_load_file() that enables/disables logging
of the hash validity (and maybe other things). The result is different
logging on startup and the rare case where ntpd finds a new leap file.
Anybody know why we want this? Anybody object if I remove it?
[ntpd restart]
7 Jan 14:12:52 ntpd[21886]: CLOCK: leapsecond file ('/etc/ntp/leap-seconds'):
good hash signature
7 Jan 14:12:52 ntpd[21886]: CLOCK: leapsecond file ('/etc/ntp/leap-seconds'):
loaded, expire=2019-06-28T00:00Z last=2017-01-01T00:00Z ofs=37
[ntpd finds a new leap file]
7 Jan 21:12:52 ntpd[21886]: CLOCK: leapsecond file ('/etc/ntp/leap-seconds'):
loaded, expire=2019-12-28T00:00Z last=2017-01-01T00:00Z ofs=37
--
These are my opinions. I hate spam.
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
