Note that this
is an instance of ntpd syncing against a single stratum 1 server.
Other configurations may have behaved differently.
Thank you for bringing this information to freshen up my understanding
of the leap second and possible implications.
This also reinvigorated my interest in an
Interestingly enough, logging reports 1 big jump on my boxes about 1.5
hours after midnight. It's curious that there's only a report of a ~1s
jump, then skew correction. Times are in UTC. I'm using constraints
from google and pool.ntp.org as the server on 5.7/amd64.
Jul 1 01:36:01 x
On Wed, Jul 01, 2015 at 02:12:48PM +, li...@ggp2.com wrote:
Interestingly enough, logging reports 1 big jump on my boxes about 1.5
Nah, that's not a jump. The message means: starting slowing
down/speeding up the clock to compensate. It takes a while for the
adjustment to be done. Once the
On 2015-06-27, Christian Weisgerber na...@mips.inka.de wrote:
After the leap second, your OpenBSD system's time will be off by,
well, one second. Gasp, shock. Let's say you synchronize your
clock with ntpd against a server that does have the correct time.
At the next poll, i.e. within about
On Wed, Jul 01, 2015 at 10:28:42AM -0400, Peter Pauly wrote:
Would you mind sharing your ntpd.conf file?
ntpd.conf:
servers pool.ntp.org
constraints from https://www.google.com;
rc.conf.local:
ntpd_flags=
I'm wondering if there's a discrepancy between ntpd -d and logging?
On Wed, Jul 01, 2015 at 02:47:48PM +, li...@ggp2.com wrote:
On Wed, Jul 01, 2015 at 10:28:42AM -0400, Peter Pauly wrote:
Would you mind sharing your ntpd.conf file?
ntpd.conf:
servers pool.ntp.org
constraints from https://www.google.com;
rc.conf.local:
ntpd_flags=
I'm
On Wed, Jul 01, 2015 at 04:26:24PM +0200, Otto Moerbeek wrote:
Nah, that's not a jump. The message means: starting slowing
down/speeding up the clock to compensate. It takes a while for the
adjustment to be done. Once the clock gets closer to the time computed
from the references, the needed
7 matches
Mail list logo
