On Friday, January 30, 2015 at 8:40:01 PM UTC-7, Paul wrote: > Probably nothing wrt the Datums. The 2100 has the "apply as soon as > announced" leap second bug.
On Friday, January 30, 2015 at 9:40:02 PM UTC-7, Brian Inglis wrote: > See recent posts on timenuts archives about Datum Tymserve 2100 et al early > >leap second, checks, and fixes. Thank you both for the replies. I've not managed to get the Datum's working yet (my leap second keeps going away), but I am on the path and that is clearly the problem with those units. Back to the offset with the HP Z3801 and Z3805. This is not a leap second bug, it is something I am doing wrong on the HP; I've got two Z3805s off by 16 seconds and one Z3801 off by one second. Could anyone point me to a place to start looking? It's clearly an HP configuration issue, not an NTP issue. My guess is something to do with the position, yet the HP reports that it knows where it is. I'd appreciate any ideas or pointers. I think I am missing something simple. I'd like to get my own system properly. The Z38xx series should be very nice clocks. _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
