William Unruh un...@invalid.ca wrote:
On 2015-01-10, Rob nom...@example.com wrote:
William Unruh un...@invalid.ca wrote:
On 2015-01-09, trackeroft...@gmail.com trackeroft...@gmail.com wrote:
What do you mean It is branded? And why is that a problem?
Hello William,
1. The installer is
On 2015-01-10 11:13, Martin Burnicki wrote:
Please note that beside the NTP binaries you also need the openssl DLL in the
version
against which the binaries have been built, otherwise ntpd fails to start.
Current OpenSSL version is 1.0.1k since maintenance improved
after Heartbleed
NIST updated ftp://time.nist.gov/pub/leap-seconds.list linked to
leap-seconds.3629404800
On 2015-01-05 07:29, Marco Marongiu wrote:
Get ready, fellows. It's coming again.
-- bronto
Forwarded Message
Subject: Bulletin C number 49
Date: Mon, 05 Jan 2015 14:25:49 +0100
From:
Why do folks mention leap seconds on this list?
Why do people point to leap-seconds.NTPtimestamp instead of just
leap-seconds.list?
My five line leap second file with comments and one extra line for
(completely unnecessary) context.
#$ 3629404800
#@ 3660249600
3550089600 35 #
On 2015-01-11, Rob nom...@example.com wrote:
William Unruh un...@invalid.ca wrote:
On 2015-01-10, Rob nom...@example.com wrote:
William Unruh un...@invalid.ca wrote:
On 2015-01-09, trackeroft...@gmail.com trackeroft...@gmail.com wrote:
What do you mean It is branded? And why is that a
And this is a problem why?
Not for me to determine. The OP posted this as a problem. You asked
what it is branded means, and I explained.
Sorry, I had thought you were the OP when I responded. Note that his
definition of branded may be different from yours. And I still have no
idea
Michael Moroney moro...@world.std.spaamtrap.com wrote:
If I have a system synchronized with a public NTP source, which is
synchronized with an atomic clock that provides leap second info, and
I am watching carefully, what will happen when the leap second hits? Will
my system suddenly find
On 1/11/2015 7:16 PM, William Unruh wrote:
If that public source is responsible it will pass on to your
system the fact that there is a leapsecond, and your system will stop
for a second at the last second of June.
A system which properly implements leap seconds will do no such thing.
It will
On 2015-01-11, Michael Moroney moro...@world.std.spaamtrap.com wrote:
If I have a system synchronized with a public NTP source, which is
synchronized with an atomic clock that provides leap second info, and
I am watching carefully, what will happen when the leap second hits? Will
my system
On 2015-01-11, trackeroft...@gmail.com trackeroft...@gmail.com wrote:
And this is a problem why?
Not for me to determine. The OP posted this as a problem. You asked
what it is branded means, and I explained.
Sorry, I had thought you were the OP when I responded. Note that his
On 2015-01-12, Mike S mi...@flatsurface.com wrote:
On 1/11/2015 7:16 PM, William Unruh wrote:
If that public source is responsible it will pass on to your
system the fact that there is a leapsecond, and your system will stop
for a second at the last second of June.
A system which properly
On 1/11/2015 9:44 PM, Mike S wrote:
On 1/11/2015 7:16 PM, William Unruh wrote:
If that public source is responsible it will pass on to your
system the fact that there is a leapsecond, and your system will stop
for a second at the last second of June.
A system which properly implements leap
On 1/11/2015 10:40 PM, William Unruh wrote:
On 2015-01-12, Mike S mi...@flatsurface.com wrote:
On 1/11/2015 7:16 PM, William Unruh wrote:
If that public source is responsible it will pass on to your
system the fact that there is a leapsecond, and your system will stop
for a second at the
On 1/11/2015 4:56 PM, Rob wrote:
Michael Moroney moro...@world.std.spaamtrap.com wrote:
If I have a system synchronized with a public NTP source, which is
synchronized with an atomic clock that provides leap second info, and
I am watching carefully, what will happen when the leap second
Brian Inglis wrote:
On 2015-01-10 11:13, Martin Burnicki wrote:
Please note that beside the NTP binaries you also need the openssl DLL
in the version
against which the binaries have been built, otherwise ntpd fails to
start.
Current OpenSSL version is 1.0.1k since maintenance improved
after
If I have a system synchronized with a public NTP source, which is
synchronized with an atomic clock that provides leap second info, and
I am watching carefully, what will happen when the leap second hits? Will
my system suddenly find its clock off by 1 second and slowly drift to
the accurate
On Sun, Jan 11, 2015 at 11:34 PM, brian utterback
brian.utterb...@oracle.com wrote:
On 1/11/2015 10:40 PM, William Unruh wrote:
Well, actually as I understand it, ntpd does stop the cclock for that
second
That is not the case. That is the behavior that the kernel reference
code
On 2015-01-12, brian utterback brian.utterb...@oracle.com wrote:
On 1/11/2015 10:40 PM, William Unruh wrote:
On 2015-01-12, Mike S mi...@flatsurface.com wrote:
On 1/11/2015 7:16 PM, William Unruh wrote:
If that public source is responsible it will pass on to your
system the fact that there
On 2015-01-11 14:31, Martin Burnicki wrote:
Brian Inglis wrote:
On 2015-01-10 11:13, Martin Burnicki wrote:
Please note that beside the NTP binaries you also need the openssl DLL
in the version against which the binaries have been built, otherwise
ntpd fails to start.
Current OpenSSL
19 matches
Mail list logo
