In message <[EMAIL PROTECTED]>, Jim King writes:
>M. Warner Losh wrote:
>
>>We started seeing the GPS future leap second being broadcast today
>>here. Just as a sanity check, are others seeing it as well?
>>
>>Warner
>>
>>
>
>I noticed it yesterday in my ntpd clockstats file, although in a
>somewhat alarming fashion:
>
>53586 1.311 127.127.30.0 ONCORE[0]: Leap second (1) scheduled for
>1Feb2006 at 0:0:0
>
>It appears that either ntpd or my Oncore (an M12 V1.3) thinks that the
>leap second is a month later than what everybody else thinks.
I bet that is the usual struct tm bug:
int tm_mon; /* month of year (0 - 11) */
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
time-nuts mailing list
time-nuts@febo.com
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
