Paul tik-...@bodosom.net wrote:
On Thu, Jan 15, 2015 at 4:40 PM, Terje Mathisen terje.mathi...@tmsw.no
wrote:
Not in my msg, but in the subject of the entire thread. :-)
I'm so used to nomail@example being wrong I had a knee-jerk reaction. My
bad.
You just can't stand being pointed at
Terje Mathisen wrote:
OK, so exactly as encoded in the right zone info, there is no leap
second until the table is updated/patched.
And yet there is no expiration date in the TZDB's leap second file
(which is also used for the right time zones), so you don't know if
there is no upcoming leap
Magnus Danielson wrote:
Hi,
On 01/15/2015 03:06 AM, Harlan Stenn wrote:
I'm trying to figure out if anybody is actively using autokey, in a
production deployment.
If you are, please let me know - I have some questions for you.
We use it to pull leap-second info off the NTP servers.
It
On 2015-01-16, Chris Adams cmad...@cmadams.net wrote:
Once upon a time, Phil W Lee p...@lee-family.me.uk said:
For the tiny number of programs which really need UTC (not TAI), it
would just be a different number, but the only thing I know of which
really needs UTC rather than TAI would be
Re. the Fitlet: With a 3.9 to 4.5 W power budget this box will never get
into those ranges, but even handling 1K requests/second with sub-ms jitter
and delay would still be a very nice Pool server.
A Raspberry PI can do 1500 packets per second.
That's a simple measurement with one request
On 01/16/2015 05:41 AM, Chris Adams wrote:
I think one problem with OS clocks in TAI is that counting it correctly
requires active/on-going maintenance at unknownable intervals for all
systems that use any form of timestamps (including for example anything
that uses network file systems).
Never tell a person he is wrong ...
Carnegie, Dale (1981). How to Win Friends Influence People. New
York, Pocket Books (Simon Shuster).
Note the word influence in the book title. If one want to make this a
better world, then one wants influence, not a reputation for being
impossible
We were using autokey at our public ntp servers(1) since 2011. We are
now in the middle of a process to deactivate it, since 4.2.8 is broken
(we could not make autokey work with 4.2.8 on Linux, it seems to be some
issue related to the version 1.0.x of openssl).
Probably we will let it
On Fri, Jan 16, 2015 at 2:02 AM, Terje Mathisen terje.mathi...@tmsw.no
wrote:
Anyway it is definitely possible to get into the 100K to 1M
requests/second range.
As I noted above the real problem isn't in the actual packet processing,
which can be made very efficient indeed for the normal
On Fri, Jan 16, 2015 at 9:02 AM, Charles Elliott elliott...@comcast.net
wrote:
Never tell a person he is wrong ...
I'm not sure what your point is but that statement is ridiculous. Frequent
and immediate correction is the PLL we want here. Wrong answers don't help
anyone.
By the way, you
Paul tik-...@bodosom.net wrote:
By the way, you can't send mail to nom...@example.com. I'm sure being
somewhat anonymous enables statements like Harlan has decided to keep us
in the dark and feed us shit..
That was VERY TRUE on that topic!!
He did not tell us what was wrong and he grossly
Hal Murray wrote:
Re. the Fitlet: With a 3.9 to 4.5 W power budget this box will never get
into those ranges, but even handling 1K requests/second with sub-ms jitter
and delay would still be a very nice Pool server.
A Raspberry PI can do 1500 packets per second.
OK, that's pretty nice
Jochen Bern writes:
...
We all know that the current NTP protocol leans toward UTC, and
doesn't address any leap seconds except the one that might be at hand
right now. In recent posts to this list, I've read about plans for an
NTPng that allows for different timescales, but still suggests
Martin,
If a fix is found for this in time I'll get it in 4.2.8p1.
H
Martin Burnicki writes:
I've just ran a few leap second tests with ntpd 4.2.8 under Windows and
Linux and found that the leap second is not applied correctly under
Windows 8 and 8.1.
Under windows 7 and on a Linux
Antonio,
Antonio M. Moreiras writes:
We were using autokey at our public ntp servers(1) since 2011. We are
now in the middle of a process to deactivate it, since 4.2.8 is broken
(we could not make autokey work with 4.2.8 on Linux, it seems to be some
issue related to the version 1.0.x of
Hi:
We were looking to use an older Trimble Thunderbolt 8 channel GPS receiver for
providing a Stratum 1 time reference. I realize this is discussed on the ntp.org
web site but sadly, the link to Trimble to get the driver (any any ntp driver)
are now all dead links.
We have it connected to
On Fri, Jan 16, 2015 at 7:49 PM, Oceanos Admin sysad...@cellmail.com
wrote:
Hi:
We were looking to use an older Trimble Thunderbolt 8 channel GPS receiver
for providing a Stratum 1 time reference
The standard hobbyist T-Bolt management program is Lady Heather. It a
windows (dos) program
17 matches
Mail list logo
