r than only initially.
If you continue to have problems, consider providing the output of `ntpq
-crv -w -clpeers` redacted of any names or addresses you wish.
Cheers,
Dave Hart
e documentation on the nature
> and extent of the interleaved support and what is needed, if any, to enable
> the same etc.,
>
Dr. Mills added interleaved support sometime in the NTP 4 timeframe, but
I'm not sure exactly when. It has been around for at least 15 years, if
that helps.
Cheers,
Dave Hart
On Tue, 22 Aug 2023 at 18:48, Edward McGuire wrote:
> ntpq> :config restrict 17.253.2.123 ignore
> ntpq> :config unpeer 17.253.2.123
>
> ultimately doesn't work. The "unpeer" drops the pool peer, but later the
> pool peer is "rediscovered" despite the "restrict ignore". Apparently the
> client
On Tue, 22 Aug 2023 at 18:48, Edward McGuire wrote:
> I'm coming back to this issue because the solution I tried:
>
> ntpq> :config restrict 17.253.2.123 ignore
> ntpq> :config unpeer 17.253.2.123
>
> ultimately doesn't work. The "unpeer" drops the pool peer, but later the
> pool peer is
I'm sorry, somehow I didn't see your Aug 1 email until now. Digging around
in this thread and in the bug report, I'm having trouble finding the
ntp.conf for reproducing the problem that you mentioned.
Thanks,
Dave Hart
On Wed, 16 Aug 2023 at 22:49, Edward McGuire wrote:
> Dave --
>
>
On Mon, 31 Jul 2023 at 16:39, Edward McGuire wrote:
> On Friday, July 28, 2023 at 9:48:35 PM UTC, Dave Hart wrote:
> > You can do the equivalent using ntpq's remote configuration command
> ":config".
> > ntpq -c "keyid 99" -c "passwd myntpqpasswd"
config restrict
10.11.12.13"
to remove the specific restriction for that address, leaving it restricted
by any more general subnet restriction or the default restriction. The
syntax for ntpq's :config is the same as for ntp.conf.
--
Cheers,
Dave Hart
t at https://people.ntp.org/hart/ntp-stable-617-2.tar.gz
Thanks,
Dave Hart
On Fri, 14 Jul 2023 at 16:52, Dave Hart wrote:
> For at least 17 years folks have asked for ntpd to re-resolve hostnames
> given in ntp.conf. For the limited case of "pool", that's been done for
> over a deca
gs.ntp.org, or to questions@lists.ntp.org,
or directly to me at daveh...@gmail.com or h...@ntp.org. Find it at:
https://people.nwtime.org/hart/ntp-stable-617.tar.gz
Thanks in advance,
Dave Hart
o be an appropriate default, and I
argue there's no need to provide an opposite "allpeers" or whatever to
retain the current "peers" behavior. If you disagree, please speak up!
--
Cheers,
Dave Hart
On Friday, June 9, 2023 at 7:10:13 AM UTC, Roger wrote:
> On Thu, 08 Jun 2023 15:05:42 +0100, Roger
> wrote:
>
> >Does ntp-4.2.8p16 have the voting code in it which
> >ntp-dev-3792-msm and ntp-dev-3792-msm-v2 has? Dave
> >Hart recently posted links to tarballs with
On Monday, June 19, 2023 at 11:57:31 AM UTC, Roger wrote:
> On Sun, 28 May 2023 13:43:00 - (UTC), "Dave Hart"
> wrote:
>
> >I've posted a new tarball, but it may not appear for a few minutes. It
> >should resolve the build failure you saw.
> >
>
On Sun, 28 May 2023 at 12:25, Dave Hart wrote:
> On Wednesday, May 24, 2023 at 5:42:20 PM UTC-4, Roger wrote:
> > Make failed on the very elderly system I'm trying the dev on
> > with the message that I needed to add -fPIC to CFLAGS.
>
> Martin Burnicki ran into the same pr
maxpoll of 17 makes sense. That's also a situation where
"burst" (not iburst) makes sense as it sends several queries each poll, giving
more samples to the clock filter process to hold over ntpd for the
day-and-a-half poll 17.
Cheers,
Dave Hart
--
This is questions@lists.ntp
On Wednesday, May 24, 2023 at 5:42:20 PM UTC-4, Roger wrote:
> On Wed, 24 May 2023 19:23:00 - (UTC), "Dave Hart"
> wrote:
>
> >Feedback from a helpful tester that they didn't see the removal of peers in
> >their log prompts me to add that you might
On Mon, 22 May 2023 at 03:42, Dave Hart wrote:
>
> After a bunch of testing myself, I’d appreciate others willing to donate
> some time to try out the new code and help work out any remaining kinks.
> Obviously pool clients using ntpd are prime candidates to test this. Those
&g
help me convince Microsoft this should be
investigated by upvoting the Feedback Hub issue I opened. I presume this
link will work only from a Windows 10 or 11 machine:
https://aka.ms/AAkyamq
Cheers,
Dave Hart
addresses, while the
second one will get IPv6 addresses.
Thanks for your time and assistance.
Cheers,
Dave Hart
stions@lists.ntp.org is most
welcome, even if only to say you’ve tried it and didn’t have any issues, so
I get a feel for how much testing has been done.
Thanks in advance!
Dave Hart
P.S. To those seeinig this on the comp.protocols.time.ntp newsgroup, if
you like you can subscribe to the linked mailin
to work indefinitely. If you notice any problems as a
result, please let me know.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
?
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On Sun, Nov 25, 2012 at 06:25 UTC, David Taylor wrote:
On 24/11/2012 20:26, Dave Hart wrote:
On Sat, Nov 24, 2012 at 7:56 PM, David Taylor
david-tay...@blueyonder.co.uk.invalid wrote:
[...]
I really can't imagine that such a low-powered server is /that/ good -
better than a nanosecond
response, but my email time
budget is severely limited through the end of year.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
(such as \Program Files (x86)\ntp\bin).
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
... was fed to
reporting the effective value after rounding -- otherwise, ntpd is
stuck trying to infer the effective clock tick size on an ongoing
basis, so the rounding can be anticipated and worked around.
Cheers,
Dave Hart
Cheers,
Dave Hart
will it be repaired, at least not
until the following major version. This willingness to foist
regressions on customers while rejecting the possibility of fixes is
incredibly sad for me personally.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
servers to
handle the client load while minimizing traffic to the S1s -- there is
very little difference in time service quality from S2s on the same
LAN as their S1 sources.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http
. Either remove the driver
or add remote sources to ensure the leap vote is won.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
or earlier
leap behavior, as I haven't used 4.2.4 in a number of years.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
not
wire the PPS signal through to DCD or another suitable input
handshaking line on their serial-to-USB chip. Thanks to Eric
Raymond's bufferbloat-related efforts, there is hope we will see PPS
exposed on more USB GPSes in the future, however.
Cheers,
Dave Hart
there. The default is tinker step 0.128
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
srcadr=95.130.12.88, leap=01
srcadr=95.211.11.181, leap=01
srcadr=95.211.7.153, leap=01
srcadr=98.191.213.7, leap=01
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
be customized with tos maxdist:
http://www.eecis.udel.edu/~mills/ntp/html/miscopt.html#tos
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
of July, so I won't be as responsive. Your help is welcome.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
+manycast mesh.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
What could be the problem? perhaps the pps signal configuration?
config.log will tell you for sure, but my guess would be you are
missing the timepps.h header file that provides Linux PPSAPI.
Cheers,
Dave Hart
___
questions mailing list
questions
.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
:03:45 ntpd[2272]: 2001:4f8:fff7:1::17 962a 8a sys_peer
1 Jul 00:12:29 ntpd[2272]: 0.0.0.0 061c 0c clock_step -1.006282 s
(followed by re-initializing interpolation spew normally seen only at startup)
You may need to add +sysall or more narrowly +sysevent to
logconfig in ntp.conf.
Cheers,
Dave
to ever use older
versions, you can abbreviate:
logconfig =allall
The default without logconfig is:
logconfig =syncall
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
be more stable over v4 or v6
at any given time, there's little lost in my opinion in failing to
treat the IPv4 and IPv6 addresses of a single server as duplicates of
each other.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http
, the Linux livelock couldn't occur as the faulty code
wouldn't be exercised. The same is true regarding the older Linux
deadlock bug hit at the moment of insertion while trying to log the
message with the :60 reference.
Cheers,
Dave Hart
___
questions
127.127.20.1 $GPGGA,001232
56109 769.317 127.127.20.1 $GPGGA,001248
Somewhere between 00:12:12 and 00:12:32 it became enlightened. Seems
I'll be temporarily switching off the NMEA+PPS driver in favor of ATOM
numbered by NTP, if I am still using the 18x LVC next leap second.
Cheers,
Dave Hart
On Sat, Jun 30, 2012 at 21:43 UTC, Dave Hart h...@ntp.org wrote:
Linux kernels 2.6.26 and later are reported at risk of livelock the
day preceding the leap insertion. I haven't found the first version
number with the fix.
http://news.ycombinator.com/item?id=4183122 indicates 3.4 is the first
slew) happened but there's no message about disarming. Also
both the leap_event and the insertion are relatively late:
1 Jul 00:00:33 ntpd[10184]: Inserting positive leap second.
1 Jul 00:00:57 ntpd[10184]: 0.0.0.0 061b 0b leap_event
There's clearly still work to do.
Cheers,
Dave Hart
-high-rates-of-linux-server-crashes-today
and mentioned there:
http://lkml.indiana.edu/hypermail/linux/kernel/1203.1/04598.html
The Red Hat knowledge base article wasn't updated a moment ago when I checked.
Cheers,
Dave Hart
___
questions mailing list
the driftfile again
and restart ntpd.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
polling intervals. With the default maximum interval of 1024 seconds
being about 17 minutes, by 00:34 30-June UTC most systems should have
picked it up that will.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org
UTC.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
ntpq -c rv.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On Thu, Jun 7, 2012 at 6:21 AM, Steve Kostecke koste...@ntp.org wrote:
On 2012-06-07, Dave Hart h...@ntp.org wrote:
I am aware of no part of the ntpd tarballs that is solely licensed
under GPL. libopts is dual-licensed BSD or GPL at user's choice. The
rest of the package is BSD-style
and jitter in the same range
are to be expected.
The output of:
ntpq -c rv 0 version precision
would shed a bit more light on which ntpd version and the time to read
the clock on that system.
Cheers,
Dave Hart
___
questions mailing list
questions
-- ampersand shorthand for association IDs start with 1.
FYI, older versions of ntpq require lpeers, lassoc, or similar before
references work. Newer ones (including 4.2.6 I believe) always
support references and will silently first issue lassoc to learn the
association IDs if needed.
Cheers,
Dave Hart
On Fri, Jun 8, 2012 at 12:17 AM, Brian Utterback
brian.utterb...@oracle.com wrote:
On 6/7/2012 7:35 PM, Dave Hart wrote:
On Thu, Jun 7, 2012 at 10:47 PM, Brian Utterback
brian.utterb...@oracle.com wrote:
(Some day it would be nice if mrv09 worked the way you expected, but
would you
PPM.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
that is solely licensed
under GPL. libopts is dual-licensed BSD or GPL at user's choice. The
rest of the package is BSD-style, as seen on the pages above. If you
are aware of any GPL-only code we're distributing, please speak up so
that we can correct the mistake.
Cheers,
Dave Hart
with the latest ntpd, I claim sntp + ntpd
can do whatever ntpdate + ntpd is used for today.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
.
Good luck,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On Tue, May 29, 2012 at 17:54 UTC, Nicolas Braud-Santoni wrote:
ntpd[18653]: ntpd 4.2.6p2@1.2194-o Sun Oct 17 13:35:13 UTC 2010 (1)
ntpd[18654]: proto: precision = 0.220 usec
ntpd[18654]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
ntpd[18654]: Listen and drop on 1 v6wildcard :: UDP 123
On Tue, May 29, 2012 at 11:01 PM, Nicolas Braud-Santoni wrote:
2012/5/30 Dave Hart h...@ntp.org:
Steve Kostecke maintains Debian packages of current ntp-dev that
should integrate more easily than building from source by hand. Check
out:
http://packages.ntp.org/debian/
There seem
/discover.html
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
with 4.2.6p5 or the latest 4.2.7, I'd love to fix
it. There may be a need to specially handle the case where upstream
LI is seen but UTC midnight has passed since the sample in question.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http
configuration. For orphan mode to operate as intended, all
participants must see all others as direct peers.
If it goes well, one host will show refid LOCL and stratum 11, the
others will all be stratum 12. If it doesn't work, please show ntpq
-c rv 0 version output.
Cheers,
Dave Hart
insertion.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
.
There may be a bug lurking in the Oncore driver your configuration
exposes, or the problem may be with the elan-mmcr PPSAPI
implementation. We don't have enough information yet.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http
for you:
interface ignore all
interface listen eth0
That should result in ntpd using only v4/v6 localhost and eth0's v4/v6
addresses.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
keeps the second source on as sys.peer (apparently forever, have
observed it for around twelve hours).
I suspect you're seeing the same issue Miroslav Lichvar reported:
http://bugs.ntp.org/1554
The fix first appeared in 4.2.7p58 and was later backported to 4.2.6p4.
Cheers,
Dave Hart
, which should become much rarer soon.
Cheers,
Dave Hart
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
5909.823 0.005407926 -77.421 0.001231754 0.014326 8
I'm not seeing anything unusual around 5300 seconds in either file.
Please enlighten me.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
around it, change the test above to:
if (0 == SRCPORT(rbufp-recv_srcadr)) {
My apology for the misinformation.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
be giving unwarranted credence to the
normally-distributed random noise referred to as fuzz whjch is
intentionally added to local clock readings.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
to the many other systems with
high-precision system clocks.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
the performance. If I did, I'd like to make ntpd use
interpolation without forcing the choice in that situation.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
, or if possible
reconfigure the NAT to avoid low source ports.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On Sat, Apr 7, 2012 at 21:36, Dave Hart h...@ntp.org wrote:
I notice the successful clients were querying using ports 123, and
the failing ones 123. I dimly recall seeing an inappropriate
less-than-123 source port comparison in ntpd long ago, in fact I'd
have guessed it had been removed
maxclock peers in the billboard (default 10). Duplicate IPs cause it
to take longer to reach maxclock, but do not affect the ultimate
number of associations assuming enough non-duplicate addresses are
available.
Cheers,
Dave Hart
___
questions mailing list
On Thu, Apr 5, 2012 at 17:30, Steve Kostecke koste...@ntp.org wrote:
On 2012-04-05, Dave Hart h...@ntp.org wrote:
Of course, neither is necessary if your local timezone is UTC to begin
with. I use UTC on my Windows systems because Windows misrepresents
historical and future timestamps which
.
Good luck,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
that keep it fail to survive to line 2688:
peers[i].peer-new_status = CTL_PST_SEL_SELCAND;
The logic in question is covered in the documentation, particularly:
http://www.eecis.udel.edu/~mills/ntp/html/cluster.html
Happy spelunking,
Dave Hart
in the clock reading path to ensure readings never go backward
without notice, as well.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
will take over.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
to use with PPSAPI. In other words, NMEA unit X
when PPSAPI is enabled looks first for /dev/gpsppsX, and if that
doesn't exist, attempts PPSAPI using the same /dev/gpsX device being
used for NMEA data.
Cheers,
Dave Hart
___
questions mailing list
can
tune time2 closer to minimize startup transients.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On Wed, Mar 28, 2012 at 05:34, A C agcarver+...@acarver.net wrote:
On 3/27/2012 22:07, Dave Hart wrote:
I suspect you will see that when you've used flag3 1, ntpd has
reported time_pps_kcbind failing. I do see a potential bug in that
code, though. If you don't get any hits from the fgrep
from
/dev/gpspps1 to /dev/pps0. This eliminates the risk of two clocks
whose confidence intervals don't overlap both being tossed as
falsetickers, as your PPS will be provided via the same refclock.
Good luck,
Dave Hart
___
questions mailing list
reachable with no prefer peer regardless of flag3.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
on line 1265:
}
Then recompile ntpd and see if it then reports time_pps_kcbind failure
with flag3 1.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
with 4.2.4, so we need a new HOWTO-type document
for 4.2.6-and-later Autokey configuration.
Good luck,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
be slightly less often
than every poll interval in case of lost traffic. Are you seeing
something else?
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On Wed, Mar 21, 2012 at 06:49, David J Taylor wrote:
(Is jitter RMS, SD, peak-to-peak?).
NTP's jitter is root mean squares of offsets from the clock filter
register (last 8 responses, more or less).
Dave Hart
___
questions mailing list
questions
On Tue, Mar 20, 2012 at 12:28, Miroslav Lichvar mlich...@redhat.com wrote:
On Tue, Mar 20, 2012 at 02:59:12AM +, Dave Hart wrote:
Although it's the first time I've seen such, it appears the offset and
frequency calculations both ended up overflowing. I would have
guessed bad input should
on the
far-more-prevalent POSIX ntpd systems porting it to Windows is pretty
far down my list.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On Tue, Mar 20, 2012 at 15:55, David J Taylor wrote:
How does NTPD_TICKADJ_PPM affect this? If that was set to -800, for
example, wouldn't the adjustment range be -300/-1300 rather than +/-500?
Yes, it would.
Cheers,
Dave Hart
___
questions mailing
the
response size, and particularly for plain readvar 0 or readvar
assoc returning a list of default variables, risk splitting the
response into multiple 500-ish byte UDP packets.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http
On Tue, Mar 20, 2012 at 17:28, unruh un...@invalid.ca wrote:
On 2012-03-20, Dave Hart h...@ntp.org wrote:
David Taylor is right that it is normal for Windows to keep running
the clock at whatever rate was last set after the program setting the
rate goes away. It's also true that Windows does
or stopped sending or sent sentences indicating no lock,
based on the last peerstats entry for 127.127.20.5 occurring almost
exactly 5 minutes before the overflow event.
Probably we should just write it off as nominal since the PC is
described as psycho.
Take care,
Dave Hart
On Tue, Mar 20, 2012 at 01:59
luck,
Dave Hart
On 3/19/2012 10:59 PM, Dave Hart wrote:
Ron,
I don't know what the heck happened either, but there are a few clues.
You didn't tell us which version of ntpd you're using or which OS
it's running on. Skimming the huge ntp.conf for non-comment lines I
see it appears
will not change
the offset estimate for that peer, as an older entry in the clock
filter register is preferred over the latest.
Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
, all leap insertions have been scheduled on the preferred
January 1 or July 1 dates, but the IERS notices could in the future
schedule a leap second insertion or deletion on the less-preferred
April 1 or October 1 dates.
Thanks for your time,
Dave Hart
approach works,
if you have configured a key id and passphrase for remote
administration via ntpq (controlkey, trustedkeys, and keys in
ntp.conf):
ntpq -c :config server 127.127.22.0 minpoll 4
Which prompts for the keyid and password to authenticate the change.
Cheers,
Dave Hart
though it has a same offset as PPS?
Are both drivers using the same PPS signal? If so, what do you hope
to gain? I'd get rid of the PPS(0) in that case and you should see
the o ornament GPS_NMEA(0).
Cheers,
Dave Hart
___
questions mailing list
questions
1 - 100 of 639 matches
Mail list logo
