Re: [time-nuts] FreeBSD 7 ntp server
> > > I'm thinking about, for example, stock trading where the first bid wins. > Sub-second resolution is needed there, I think. Advanced Message Queuing Protocol (AMQP) is what is used in some big brokerage firms. http://jira.amqp.org/confluence/display/AMQP/Advanced+Message+Queuing+Protocol Specs are here: http://jira.amqp.org/confluence/display/AMQP/Download The datetime type encodes a date and time using the 64 bit POSIX time_t format. Also http://cr.yp.to/time.html maybe of interest to Time Nuts. -- http://www.wearablesmartsensors.com/ http://www.softwaresafety.net/ http://www.designer-iii.com/ http://www.unusualresearch.com/ ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] FreeBSD 7 ntp server
In message: <1231b6a80812312047k5d2d702djcdd9610f47bc9...@mail.gmail.com> "Steve Rooke" writes: : 2009/1/1 M. Warner Losh : : > In message: : >Neon John writes: : > : On Wed, 31 Dec 2008 17:57:33 -0700 (MST), "M. Warner Losh" : > : wrote: : > : : > : >In message: : > : >"Robert Darlington" writes: : > : >: Okay, not very fun. I was hoping to see ...58,59,60,00. Instead my : > : >: system ticked :59 twice.Here's the output of my not so very : > : >: scientific logs (up arrow, enter, over and over): : > : > : > : >That's the correct output. It isn't possible to tick 60 with a POSIX : > : >time_t, so second 59 is replayed so that we don't cross a day : > : >boundary. : > : > : > : >Warner : > : > : > : : > : I wonder how application software handled that. Say, a transaction processing : > : machine handling a few thousand transactions a second where the time stamp : > : matters. What did the high res timer do? : > : > Same thing it normally does... : > : > : I'm thinking about, for example, stock trading where the first bid wins. : > : Sub-second resolution is needed there, I think. : > : > That's one of many reasons why I think that leap seconds are : > fundamentally incompatible with POSIX. : > : > : I wonder if this was a mini-Y2K and folks haven't realized it yet? : : Seems to have worked perfectly under OpenSUSE 11.1, kernel 2.6.27, : with NTP here. It's just the poor Windblows systems that I worry : about. Actually, most of the effects on systems that use an absolute time for timeouts. posix threads can cause a stutter of 1s. This can be quite hard to detect in many systems, but very bad in others... Warner ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] FreeBSD 7 ntp server
2009/1/1 M. Warner Losh : > In message: >Neon John writes: > : On Wed, 31 Dec 2008 17:57:33 -0700 (MST), "M. Warner Losh" > : wrote: > : > : >In message: > : >"Robert Darlington" writes: > : >: Okay, not very fun. I was hoping to see ...58,59,60,00. Instead my > : >: system ticked :59 twice.Here's the output of my not so very > : >: scientific logs (up arrow, enter, over and over): > : > > : >That's the correct output. It isn't possible to tick 60 with a POSIX > : >time_t, so second 59 is replayed so that we don't cross a day > : >boundary. > : > > : >Warner > : > > : > : I wonder how application software handled that. Say, a transaction > processing > : machine handling a few thousand transactions a second where the time stamp > : matters. What did the high res timer do? > > Same thing it normally does... > > : I'm thinking about, for example, stock trading where the first bid wins. > : Sub-second resolution is needed there, I think. > > That's one of many reasons why I think that leap seconds are > fundamentally incompatible with POSIX. > > : I wonder if this was a mini-Y2K and folks haven't realized it yet? Seems to have worked perfectly under OpenSUSE 11.1, kernel 2.6.27, with NTP here. It's just the poor Windblows systems that I worry about. 73, Steve -- Steve Rooke - ZL3TUV & G8KVD & JAKDTTNW Omnium finis imminet ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] FreeBSD 7 ntp server
In message: Neon John writes: : On Wed, 31 Dec 2008 17:57:33 -0700 (MST), "M. Warner Losh" : wrote: : : >In message: : >"Robert Darlington" writes: : >: Okay, not very fun. I was hoping to see ...58,59,60,00. Instead my : >: system ticked :59 twice.Here's the output of my not so very : >: scientific logs (up arrow, enter, over and over): : > : >That's the correct output. It isn't possible to tick 60 with a POSIX : >time_t, so second 59 is replayed so that we don't cross a day : >boundary. : > : >Warner : > : : I wonder how application software handled that. Say, a transaction processing : machine handling a few thousand transactions a second where the time stamp : matters. What did the high res timer do? Same thing it normally does... : I'm thinking about, for example, stock trading where the first bid wins. : Sub-second resolution is needed there, I think. That's one of many reasons why I think that leap seconds are fundamentally incompatible with POSIX. : I wonder if this was a mini-Y2K and folks haven't realized it yet? :) Warner : John : -- : John De Armond : See my website for my current email address : http://www.neon-john.com : http://www.johndearmond.com <-- best little blog on the net! : Tellico Plains, Occupied TN : Alcohol, Tobacco & Firearms should be a convenience store, not a government agency. : : : ___ : time-nuts mailing list -- time-nuts@febo.com : To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts : and follow the instructions there. : : ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] FreeBSD 7 ntp server
On Wed, 31 Dec 2008 17:57:33 -0700 (MST), "M. Warner Losh" wrote: >In message: >"Robert Darlington" writes: >: Okay, not very fun. I was hoping to see ...58,59,60,00. Instead my >: system ticked :59 twice.Here's the output of my not so very >: scientific logs (up arrow, enter, over and over): > >That's the correct output. It isn't possible to tick 60 with a POSIX >time_t, so second 59 is replayed so that we don't cross a day >boundary. > >Warner > I wonder how application software handled that. Say, a transaction processing machine handling a few thousand transactions a second where the time stamp matters. What did the high res timer do? I'm thinking about, for example, stock trading where the first bid wins. Sub-second resolution is needed there, I think. I wonder if this was a mini-Y2K and folks haven't realized it yet? John -- John De Armond See my website for my current email address http://www.neon-john.com http://www.johndearmond.com <-- best little blog on the net! Tellico Plains, Occupied TN Alcohol, Tobacco & Firearms should be a convenience store, not a government agency. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] FreeBSD 7 ntp server
In message: "Robert Darlington" writes: : Okay, not very fun. I was hoping to see ...58,59,60,00. Instead my : system ticked :59 twice.Here's the output of my not so very : scientific logs (up arrow, enter, over and over): That's the correct output. It isn't possible to tick 60 with a POSIX time_t, so second 59 is replayed so that we don't cross a day boundary. Warner : ntp_gettime() returns code 1 (INS) : time cd0685ff.18496674 Wed, Dec 31 2008 16:59:59.094, (.094870766), : maximum error 4762 us, estimated error 15 us, TAI offset 33 : ntp_adjtime() returns code 1 (INS) : modes 0x0 (), : offset -0.278 us, frequency -0.051 ppm, interval 1 s, : maximum error 4762 us, estimated error 15 us, : status 0x2011 (PLL,INS,NANO), : time constant 4, precision 0.001 us, tolerance 496 ppm, : time# ntptime : ntp_gettime() returns code 1 (INS) : time cd0685ff.65479d28 Wed, Dec 31 2008 16:59:59.395, (.395624242), : maximum error 4762 us, estimated error 15 us, TAI offset 33 : ntp_adjtime() returns code 1 (INS) : modes 0x0 (), : offset -0.278 us, frequency -0.051 ppm, interval 1 s, : maximum error 4762 us, estimated error 15 us, : status 0x2011 (PLL,INS,NANO), : time constant 4, precision 0.001 us, tolerance 496 ppm, : time# ntptime : ntp_gettime() returns code 1 (INS) : time cd0685ff.b73eee0c Wed, Dec 31 2008 16:59:59.715, (.715804039), : maximum error 4762 us, estimated error 15 us, TAI offset 33 : ntp_adjtime() returns code 1 (INS) : modes 0x0 (), : offset -0.278 us, frequency -0.051 ppm, interval 1 s, : maximum error 4762 us, estimated error 15 us, : status 0x2011 (PLL,INS,NANO), : time constant 4, precision 0.001 us, tolerance 496 ppm, : time# ntptime : ntp_gettime() returns code 3 (OOP) : time cd0685ff.03fb7a60 Wed, Dec 31 2008 16:59:59.015, (.015556955), : maximum error 5262 us, estimated error 15 us, TAI offset 34 : ntp_adjtime() returns code 3 (OOP) : modes 0x0 (), : offset -0.277 us, frequency -0.051 ppm, interval 1 s, : maximum error 5262 us, estimated error 15 us, : status 0x2011 (PLL,INS,NANO), : time constant 4, precision 0.001 us, tolerance 496 ppm, : time# ntptime : ntp_gettime() returns code 3 (OOP) : time cd0685ff.50d0bb50 Wed, Dec 31 2008 16:59:59.315, (.315685712), : maximum error 5262 us, estimated error 15 us, TAI offset 34 : ntp_adjtime() returns code 3 (OOP) : modes 0x0 (), : offset -0.277 us, frequency -0.051 ppm, interval 1 s, : maximum error 5262 us, estimated error 15 us, : status 0x2011 (PLL,INS,NANO), : time constant 4, precision 0.001 us, tolerance 496 ppm, : time# ntptime : ntp_gettime() returns code 3 (OOP) : time cd0685ff.9d5dc3c8 Wed, Dec 31 2008 16:59:59.614, (.614712868), : maximum error 5262 us, estimated error 15 us, TAI offset 34 : ntp_adjtime() returns code 3 (OOP) : modes 0x0 (), : offset -0.277 us, frequency -0.051 ppm, interval 1 s, : maximum error 5262 us, estimated error 15 us, : status 0x2011 (PLL,INS,NANO), : time constant 4, precision 0.001 us, tolerance 496 ppm, : time# ntptime : ntp_gettime() returns code 3 (OOP) : time cd0685ff.ef985218 Wed, Dec 31 2008 16:59:59.935, (.935918664), : maximum error 5262 us, estimated error 15 us, TAI offset 34 : ntp_adjtime() returns code 3 (OOP) : modes 0x0 (), : offset -0.277 us, frequency -0.051 ppm, interval 1 s, : maximum error 5262 us, estimated error 15 us, : status 0x2011 (PLL,INS,NANO), : time constant 4, precision 0.001 us, tolerance 496 ppm, : time# ntptime : ntp_gettime() returns code 4 (WAIT) : time cd068600.4e4a6a6c Wed, Dec 31 2008 17:00:00.305, (.305823220), : maximum error 5762 us, estimated error 15 us, TAI offset 34 : ntp_adjtime() returns code 4 (WAIT) : modes 0x0 (), : offset -0.276 us, frequency -0.051 ppm, interval 1 s, : maximum error 5762 us, estimated error 15 us, : status 0x2011 (PLL,INS,NANO), : time constant 4, precision 0.001 us, tolerance 496 ppm, : : ___ : time-nuts mailing list -- time-nuts@febo.com : To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts : and follow the instructions there. : : ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] FreeBSD 7 ntp server
Okay, not very fun. I was hoping to see ...58,59,60,00. Instead my system ticked :59 twice.Here's the output of my not so very scientific logs (up arrow, enter, over and over): ntp_gettime() returns code 1 (INS) time cd0685ff.18496674 Wed, Dec 31 2008 16:59:59.094, (.094870766), maximum error 4762 us, estimated error 15 us, TAI offset 33 ntp_adjtime() returns code 1 (INS) modes 0x0 (), offset -0.278 us, frequency -0.051 ppm, interval 1 s, maximum error 4762 us, estimated error 15 us, status 0x2011 (PLL,INS,NANO), time constant 4, precision 0.001 us, tolerance 496 ppm, time# ntptime ntp_gettime() returns code 1 (INS) time cd0685ff.65479d28 Wed, Dec 31 2008 16:59:59.395, (.395624242), maximum error 4762 us, estimated error 15 us, TAI offset 33 ntp_adjtime() returns code 1 (INS) modes 0x0 (), offset -0.278 us, frequency -0.051 ppm, interval 1 s, maximum error 4762 us, estimated error 15 us, status 0x2011 (PLL,INS,NANO), time constant 4, precision 0.001 us, tolerance 496 ppm, time# ntptime ntp_gettime() returns code 1 (INS) time cd0685ff.b73eee0c Wed, Dec 31 2008 16:59:59.715, (.715804039), maximum error 4762 us, estimated error 15 us, TAI offset 33 ntp_adjtime() returns code 1 (INS) modes 0x0 (), offset -0.278 us, frequency -0.051 ppm, interval 1 s, maximum error 4762 us, estimated error 15 us, status 0x2011 (PLL,INS,NANO), time constant 4, precision 0.001 us, tolerance 496 ppm, time# ntptime ntp_gettime() returns code 3 (OOP) time cd0685ff.03fb7a60 Wed, Dec 31 2008 16:59:59.015, (.015556955), maximum error 5262 us, estimated error 15 us, TAI offset 34 ntp_adjtime() returns code 3 (OOP) modes 0x0 (), offset -0.277 us, frequency -0.051 ppm, interval 1 s, maximum error 5262 us, estimated error 15 us, status 0x2011 (PLL,INS,NANO), time constant 4, precision 0.001 us, tolerance 496 ppm, time# ntptime ntp_gettime() returns code 3 (OOP) time cd0685ff.50d0bb50 Wed, Dec 31 2008 16:59:59.315, (.315685712), maximum error 5262 us, estimated error 15 us, TAI offset 34 ntp_adjtime() returns code 3 (OOP) modes 0x0 (), offset -0.277 us, frequency -0.051 ppm, interval 1 s, maximum error 5262 us, estimated error 15 us, status 0x2011 (PLL,INS,NANO), time constant 4, precision 0.001 us, tolerance 496 ppm, time# ntptime ntp_gettime() returns code 3 (OOP) time cd0685ff.9d5dc3c8 Wed, Dec 31 2008 16:59:59.614, (.614712868), maximum error 5262 us, estimated error 15 us, TAI offset 34 ntp_adjtime() returns code 3 (OOP) modes 0x0 (), offset -0.277 us, frequency -0.051 ppm, interval 1 s, maximum error 5262 us, estimated error 15 us, status 0x2011 (PLL,INS,NANO), time constant 4, precision 0.001 us, tolerance 496 ppm, time# ntptime ntp_gettime() returns code 3 (OOP) time cd0685ff.ef985218 Wed, Dec 31 2008 16:59:59.935, (.935918664), maximum error 5262 us, estimated error 15 us, TAI offset 34 ntp_adjtime() returns code 3 (OOP) modes 0x0 (), offset -0.277 us, frequency -0.051 ppm, interval 1 s, maximum error 5262 us, estimated error 15 us, status 0x2011 (PLL,INS,NANO), time constant 4, precision 0.001 us, tolerance 496 ppm, time# ntptime ntp_gettime() returns code 4 (WAIT) time cd068600.4e4a6a6c Wed, Dec 31 2008 17:00:00.305, (.305823220), maximum error 5762 us, estimated error 15 us, TAI offset 34 ntp_adjtime() returns code 4 (WAIT) modes 0x0 (), offset -0.276 us, frequency -0.051 ppm, interval 1 s, maximum error 5762 us, estimated error 15 us, status 0x2011 (PLL,INS,NANO), time constant 4, precision 0.001 us, tolerance 496 ppm, ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
