In message <[EMAIL PROTECTED]>, Rob Seaman writes: >On Jan 14, 2006, at 8:59 AM, Richard Langley wrote: > >> The problem existed for only 2-1/2 minutes, not hours. > >Thanks for the clarification. > >> Might be coincidental with the leap second but I've not noticed >> this problem at other times. > >Would be a significant coincidence. Any simple explanation for the >90 second lag in the issue being triggered? The latency associated >with emergent behavior is of interest in itself.
As far as I recall GLONASS was messed up for hours on the previous leapsecond, so there is a good chance it is because of the leap seconds that it fell out this time. -- 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.
