In message <[email protected]>, Magnus Danielson writes:
>Of course it cannot output a correct UTC solution until it has received
>page 18 subframe 4, but it can store the leapsecond offset in
>non-volatile RAM since last lock and for most of times that would give
>correct UTC from first lock [...]
And once again, this topic reminds me of my favourite Monty Python
episode:
"This is an official announcement from the Royal Navy.
Canibalism is a problem the Royal Navy has mostly under control.
[...]
"
"most of the times" is simply not good enough.
--
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.
_______________________________________________
LEAPSECS mailing list
[email protected]
http://six.pairlist.net/mailman/listinfo/leapsecs
