Re: [LEAPSECS] Time Synchronization in Financial markets

2016-10-11 Thread Steffen Nurpmeso
Warner Losh wrote: |On Mon, Oct 10, 2016 at 12:02 AM, Hal Murray \ |wrote: ... |>> Not being a traditionalist myself, I don't feel that there is anything \ |>> wrong |>> with 23:59:60 as a label for a particular second. |> |> Unfortunately,

Re: [LEAPSECS] Time Synchronization in Financial markets

2016-10-11 Thread Martin Burnicki
Hal Murray wrote: > > i...@bsdimp.com said: >> Except, last I checked, NTP doesn't use this. And applications don't re-read >> the zone file info when they are updated, so long running applications will >> use the old data. Also, that file doesn't have then pending leap second this >> December in

Re: [LEAPSECS] Time Synchronization in Financial markets

2016-10-10 Thread Martin Burnicki
John Sauter wrote: > I took the lack of mention of leap seconds to mean that leap seconds > ere not a problem. The output of the NISTDC units is an astonishingly > accurate 1 pulse per second. That feeds NTP, which handles leap > seconds using a table. As long as the table is kept up to date,

Re: [LEAPSECS] Time Synchronization in Financial markets

2016-10-10 Thread Brooks Harris
On 2016-10-09 11:32 PM, John Sauter wrote: On Sun, 2016-10-09 at 15:12 -0400, Brooks Harris wrote: I took the lack of mention of leap seconds to mean that leap seconds ere not a problem. The output of the NISTDC units is an astonishingly accurate 1 pulse per second. That feeds NTP, which

Re: [LEAPSECS] Time Synchronization in Financial markets

2016-10-10 Thread Warner Losh
On Mon, Oct 10, 2016 at 12:02 AM, Hal Murray wrote: > >> Meantime there is no standardized way to keep the Leap Second tables >> automatically updated to begin with. > > It's being distributed with the time zone data. Hopefully, all the major > distros/OSes will include

Re: [LEAPSECS] Time Synchronization in Financial markets

2016-10-10 Thread Hal Murray
> Meantime there is no standardized way to keep the Leap Second tables > automatically updated to begin with. It's being distributed with the time zone data. Hopefully, all the major distros/OSes will include it by the end of the year. (Don't hold your breath.) >From Debian jessie

Re: [LEAPSECS] Time Synchronization in Financial markets

2016-10-09 Thread John Sauter
On Sun, 2016-10-09 at 15:12 -0400, Brooks Harris wrote: > > I took the lack of mention of leap seconds to mean that leap > > seconds > > ere not a problem.  The output of the NISTDC units is an > > astonishingly > >  accurate 1 pulse per second.  That feeds NTP, which handles leap > > seconds

Re: [LEAPSECS] Time Synchronization in Financial markets

2016-10-09 Thread Brooks Harris
Hi John, On 2016-10-09 12:41 PM, John Sauter wrote: On Sat, 2016-10-08 at 15:58 -0600, Warner Losh wrote: On Sat, Oct 8, 2016 at 2:43 PM, Steve Allen wrote: On Fri 2016-10-07T11:48:25 -0600, Warner Losh hath writ: Accurate, Traceable, and Verifiable Time Synchronization for

Re: [LEAPSECS] Time Synchronization in Financial markets

2016-10-09 Thread John Sauter
On Sat, 2016-10-08 at 15:58 -0600, Warner Losh wrote: > On Sat, Oct 8, 2016 at 2:43 PM, Steve Allen wrote: > > > > On Fri 2016-10-07T11:48:25 -0600, Warner Losh hath writ: > > > > > > Accurate, Traceable, and Verifiable Time Synchronization for > > > World > > > Financial

Re: [LEAPSECS] Time Synchronization in Financial markets

2016-10-08 Thread Steve Allen
On Fri 2016-10-07T11:48:25 -0600, Warner Losh hath writ: > Accurate, Traceable, and Verifiable Time Synchronization for World > Financial Markets > > http://nvlpubs.nist.gov/nistpubs/jres/121/jres.121.023.pdf > > Market synchronization requirements today are 1s. However, in August > 2017 they

[LEAPSECS] Time Synchronization in Financial markets

2016-10-07 Thread Warner Losh
This was just published with a friend as co-author: Accurate, Traceable, and Verifiable Time Synchronization for World Financial Markets http://nvlpubs.nist.gov/nistpubs/jres/121/jres.121.023.pdf Market synchronization requirements today are 1s. However, in August 2017 they become 50ms. Good