[LEAPSECS] leap second and DUT1 database

2015-01-28 Thread Tom Van Baak
Hi Warner, 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. I know

Re: [LEAPSECS] leap second and DUT1 database

2015-01-28 Thread Poul-Henning Kamp
In message D23088365D3E46A3B6C04B915AFB6920@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

Re: [LEAPSECS] leap second and DUT1 database

2015-01-28 Thread Warner Losh
On Jan 28, 2015, at 5:25 AM, Tom Van Baak t...@leapsecond.com wrote: Hi Warner, 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