[LEAPSECS] leap second and DUT1 database

[Poul-Henning Kamp]

--------
In message <D23088365D3E46A3B6C04B915AFB6920 at pc52>, "Tom Van Baak" writes:

>Keeping cold spares is a good example. I can see that having to acquire 
>GPS lock and waiting up to 12.5 minutes for current leap second 
>information would be a problem. There must be a way to cache that state 
>so rapid failover is possible, in both the hot and cold spare case.

GPS is actually the easy case, because the announce leap seconds
months in advance.

DCF77 gives you only one hour notice about the leapsecond.


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.