Leap second bug in BNC
|Reported by:||k.fenaughty||Owned by:||mervart|
We are running v2.6 of BNC. The latency calculations produced by this software have been incorrect since the leap second of July 1 2012. The bug is in the module rtcm3torinex.c which does not feature the latest leap second.
The result is that latency messages are being logged every second instead of at the proscribed interval (perfIntr), and of course the calculations are wrong (negative latencies!).