[questions] Re: NTP community feels broken

On Friday, June 17, 2022 at 2:24:05 PM UTC-4, chris wrote: > That's correct, but the various issues with the system have been > discussed for years, yet nothing ever gets done about it. That's the > point that Philip above was making... Of course working with Harlan is difficult. Coming here to

[questions] Re: NTP community feels broken

On Friday, June 17, 2022 at 2:33:35 PM UTC-4, David Woolley wrote: > On 17/06/2022 19:14, Paul G wrote: > > Where is it in this > > tarball:http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ntp-4.2/ntp-4.2.8p15.tar.gz > > > > > > If it's not there then y

[questions] Re: NTP community feels broken

On Friday, June 17, 2022 at 2:12:52 PM UTC-4, chris wrote: > Nothing to do with products. ntp.org has a monitoring system that polls > every server in its database to verify that it's reachable. Perhaps you mean pool.ntp.org. It's in the ntp.org namespace but it's a separate project run by Ask

[questions] Re: NTP community feels broken

On Friday, June 17, 2022 at 11:24:31 AM UTC-4, chris wrote: > It's the code that polls ntp servers to verify that they are up. Where is it in this tarball: http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ntp-4.2/ntp-4.2.8p15.tar.gz If it's not there then you're probably in the wrong list/group. --

[questions] Re: NTP community feels broken

On Friday, June 17, 2022 at 9:37:15 AM UTC-4, chris wrote: > The problem is the monitoring software What software product/program do you mean? -- This is questions@lists.ntp.org Subscribe: questions+subscr...@lists.ntp.org Unsubscribe: questions+unsubscr...@lists.ntp.org

Re: [ntp:questions] More than one PPS source on Raspberry Pi?

The answer is no and yes (and also maybe).. no because the current pps-gpio driver only loads a single pin (though it could be extended to load more than one, but i dont think anyones done that). yes because the other way it could be achieved is to create a second module called pps-gpio2 and

Re: [ntp:questions] Looking for a NTP stratum 2 appliance

On Mon, May 29, 2017 at 4:24 AM, François Meyer wrote: > the problem is with GPS Time, that is not UTC(USNO) and not traceable This is not correct (per USNO). "GPS Time" is traceable (in NIST usage) to UTC(USNO) and hence UTC. The GPS message carries the current offset and USNO produces retro

Re: [ntp:questions] Looking for a NTP stratum 2 appliance

On Fri, May 26, 2017 at 10:33 PM, Harlan Stenn wrote: > NIST doesn't control GPS. That's done by USNO and the USAF. > This is true(ish)* but irrelevant. NIST defines traceability to NIST and GPS can be a component of UTC(NIST) traceability. More importantly the premise of this issue is incorr

Re: [ntp:questions] Looking for a NTP stratum 2 appliance

I also assumed that despite what you wrote you were using your (too few) S1 devices. I would agree that you probably should not poll NIST at small intervals for various reasons. However I suspect that there's a deeper misunderstanding. Per NIST the US Federal GNSS system (known as the Global Pos

Re: [ntp:questions] Looking for a NTP stratum 2 appliance

"The Securities and Exchange Commission (SEC) approved a new clock synchronization standard of 50 milliseconds applicable to computer clocks that are used to record certain events in NMS securities or OTC equity securities. Firms have six months from the effective date, until February 20, 2017, to

Re: [ntp:questions] NTP under AIX?

On Thu, May 18, 2017 at 3:06 PM, Brian Inglis < brian.ing...@systematicsw.ab.ca> wrote: > A lot of these types of boxes appear to be some type of SoC board with > some GPS module, some Linux distro, some NTP release, probably GPSd, > and with little in the way of docs, specs (typical: <1us!), guar

Re: [ntp:questions] NTP under AIX?

On Thu, May 18, 2017 at 2:20 PM, Brian Inglis < brian.ing...@systematicsw.ab.ca> wrote: > JLT Fury is overkill if you don't need better than Rb performance > and stability. > Ooops. I typed JF rather than JL (Jackson Labs). I picked the Fury over the other JL products because it comes in a desk

Re: [ntp:questions] NTP under AIX?

On Thu, May 18, 2017 at 10:55 AM, Terje Mathisen wrote: > David Taylor wrote: > >> On 16/05/2017 19:53, Greg Moeller wrote: >> >>> Is there a way to test? It seems like I'm heading into the >>> unknown here. :) >>> >> >> You could get a dedicated NTP box such as: >> >> >> http://www.leobodnar.c

[ntp:questions] dynamic stratum changes

Hi, I'm setting up ntp on an isolated net. Some of our linux machines run a custom time protocol that synchronizes the kernel to GPS time to sub millisecond accuracy. I've got my ntpd.conf using the local oscillator (127.127.1.1) clock at stratum 1. I'm looking to see what I should do when my cu

Re: [ntp:questions] Testing IPv6 code

The proximate cause is using the wrong name for the pool. 2.pool.ntp.org will return IPv6. Use one of those. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions

[ntp:questions] What happened to the software of which ntimed-client was a part?

The schedule seems to have slipped. The last update with a date was maybe two years ago with some speculation that the master could be done a year ago. Did the Linux Foundation lose interest? Given the alternative I was hoping for a bit more code. ___

[ntp:questions] 4.2.8p9 build issue on ARM running Ubuntu 14.04

[conflicting types for 'EVP_MD_CTX'] I've been able to build every version for some time but I can't build 4.2.8.p9/ARM/Ubuntu 14.04 because of the changes to a_md5encrypt. I don't cross-compile. Before I start trying to figure this out I thought I'd ask if there's something obvious I've missed.

Re: [ntp:questions] Help: fudge time2 value for NMEA driver

On Thu, Nov 3, 2016 at 11:59 PM, Brian Inglis < brian.ing...@systematicsw.ab.ca> wrote: > > The JLT Fury emulates the HP/Symmetricom/Agilent/Keysight 58503 which is a > newer variant of the venerable HP38xx GPS-DOs, > Sure but this is tne NTP list and if you have a Fury you should use NMEA. The d

Re: [ntp:questions] Help: fudge time2 value for NMEA driver

On Thu, Nov 3, 2016 at 2:27 PM, Brian Inglis < brian.ing...@systematicsw.ab.ca> wrote: > > What do your refclock ntp.conf lines look like? > I'm not sure why you're asking but: # PPS (ATOM) server 127.127.22.0 minpoll 3 fudge 127.127.22.0 refid GPPS # NMEA @19200 server 127.127.20.0 minpoll 3 m

Re: [ntp:questions] Help: fudge time2 value for NMEA driver

On Sun, Oct 30, 2016 at 1:29 PM, ogre up wrote: > Hello everyone, I've setup a NMEA+PPS ntp server, but both ref clock have > strange offset value reported by ntpq -p. > Your billboard is fine. If you want less jitter in your NMEA sentences you need to buy better hardware. Not necessarily more

Re: [ntp:questions] Best NMEA sentence

On Sun, Feb 21, 2016 at 9:43 PM, Brian Inglis < brian.ing...@systematicsw.ab.ca> wrote: > To amplify: would you suggest that the spec in that case should be FreeBSD > on a > Soekris or similar with an HP primary or secondary reference clock or > similar? I can't imagine any circumstance where I

Re: [ntp:questions] Best NMEA sentence

On Sun, Feb 21, 2016 at 12:23 PM, Neil Green wrote: > A supplementary question: when searching for ways to make an NTP server > better, I find FreeBSD recommended a lot That's the result of a fundamental misunderstanding. Most people using NTP want to synchronize a network of computers in whi

Re: [ntp:questions] Best NMEA sentence

On Sat, Feb 20, 2016 at 6:58 AM, Neil Green wrote: > Is there a generally accepted NMEA “best sentence” for use with ntp? For > example, I’ve seen GPRMC ... > RMC is the best. Athough it abbreviates the year to two digits it provides a complete timestamp plus fix validity and of course unlike t

Re: [ntp:questions] Fw: NTP and Trimble TSIP

On Tue, Feb 16, 2016 at 7:40 PM, Brian Inglis < brian.ing...@systematicsw.ab.ca> wrote: > > This module specs don't mention frequency output other than 1PPS which is > specced within 60ns, so much better than almost all. If it also supports > TRAIM and sawtooth correction, the driver can improve o

Re: [ntp:questions] Fw: NTP and Trimble TSIP

st in supporting newer Trimble devices (Resolution etc.). I can send you a patch (which also fixes the smal bug in the Thunderbolt code) that I'd expect to work with the ICM if you like. Note that the consensus is that 10Mhz from from a GPS module is

Re: [ntp:questions] custom NMEA messages

On Mon, Jan 4, 2016 at 3:58 AM, Hal Murray wrote: > > On Tue, Dec 29, 2015 at 4:08 PM, Brian Inglis < > brian.ing...@systematicsw.ab.ca> wrote: > > If you are looking at NMEA message timing - that's all over the board on > > every device > > No, some devices do it right. Look at my graph (way ab

Re: [ntp:questions] Atheros AR9331 w/GPS + PPS

On 8/09/2015 5:44 pm, Gabs Ricalde wrote: On Tue, Sep 1, 2015 at 3:22 AM, Paul J R wrote: Hi All, Thought I might share my experiences. Got given a little AR9331 based router some months ago (gl.inet 6416a) and spun up pps on one of its gpio lines. Its been running for about 2 months and so

[ntp:questions] Atheros AR9331 w/GPS + PPS

many references to anyone using an Atheros chipset for pps and ntp so far but im curious if anyone else has had any experiences? Regards, Paul ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] failing-over flaky upstream servers

On Thu, Mar 12, 2015 at 2:12 PM, Paul wrote: > As you'd well > know, the PPS signal stops when the unit is tracking less than three > satellites. That's the win for a timing receiver. It will have single satellite mode. > (The whole "prior to > 4.2.8"

Re: [ntp:questions] failing-over flaky upstream servers

> A new GPSDO can be had for much less than a Cesium (Cs) or Rubidium > (Rb) standard if you do want to go that way. Well, yes. Maybe next time around! > In each case you probably want to use orphan mode. Was not aware of that. I will need to do some reading. -- Paul. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] failing-over flaky upstream servers

t you think about the local clock, if you significantly disagree with my fudge factor on driver28 and if you think the NMEA driver (20) is significantly better than the SHM driver (28) for my particular case. [1] http://doc.ntp.org/4.1.1/driver1.htm -- Paul. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] failing-over flaky upstream servers

On Thu, Mar 12, 2015 at 8:36 AM, Paul wrote: > I would like my ntpd to continue serving time, gracefully choosing > from the "best" available upstream servers. > ... > > 3. PPS signal derived from GPS. Excellent accuracy, but only > available say 90%

[ntp:questions] failing-over flaky upstream servers

-0.544 1.633 Any thoughts? How would you go about configuring ntpd for these clocks? -- Paul. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Could some one help in pointing out the error here

On Mon, Mar 2, 2015 at 4:37 AM, wrote: > I need to use the following commands in my system: > :config server > :config restrict ... > :config unconfig ... > Refer to It's :config unpeer not :config unconfig. Also note that peer has

Re: [ntp:questions] chrony as a server

On Tue, Feb 24, 2015 at 4:17 PM, William Unruh wrote: > It is superior in that you can do it easily. Whether that is of any > importance to you is of course up to you. Myself I have never used it. > As is often the case you completely miss the point. > Fine. It has already been written for chr

Re: [ntp:questions] chrony as a server

On Tue, Feb 24, 2015 at 3:22 PM, Charles Swiger wrote: > > Data is available. Feel free to review the papers referenced from: > I was unclear. I mean specific research regarding disciplining a clock via manual correction not human coordination or fine motor control. As I said, an unbiased ass

Re: [ntp:questions] chrony as a server

On Tue, Feb 24, 2015 at 1:14 PM, Charles Swiger wrote: > On Feb 23, 2015, at 11:57 PM, David Woolley > wrote: > > On 23/02/15 21:23, William Unruh wrote: > >> manual corrections are probably good to 1 sec. > > > > It's a long time since I did this, but 200ms is more like it > > However, if you t

Re: [ntp:questions] chrony as a server

On Mon, Feb 23, 2015 at 12:53 PM, William Unruh wrote: > As Lichvar says with chrony > you periodically read your watch, or listen to radio, and set the time > and chrony figures out that you have a drift rate of about 30PPM and > corrects. Now you may not value that possibility, which is perfect

Re: [ntp:questions] chrony as a server

On Sat, Feb 21, 2015 at 1:57 AM, William Unruh wrote: > > On 2015-02-21, Paul wrote: > > On Fri, Feb 20, 2015 at 3:23 PM, William Unruh wrote: > > > >> ??? how do assume that the chrony docs do not tell the truth? > ^ you > Okay, I'll assum

Re: [ntp:questions] chrony as a server

On Fri, Feb 20, 2015 at 3:23 PM, William Unruh wrote: > ??? how do assume that the chrony docs do not tell the truth? I don't understand that sentence. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Pool server gone wild

On Fri, Feb 20, 2015 at 6:21 PM, Harlan Stenn wrote: > This is interesting. It may be that only 4 responses are returned at a > time, but there has been lots of evidence and experience that depending > on your resolver (most resolvers, from what I've seen), you won't get > the same responses eac

Re: [ntp:questions] NTP with 2 servers

On Fri, Feb 20, 2015 at 3:17 PM, Nuno Pereira wrote: > I know how NTP works > (http://www.ntp.org/ntpfaq/NTP-s-algo-real.htm#Q-NTP-ALGO), and so this > seems > to be caused by both 2 servers or just 1 of them not have survived. > As recently noted the ntpfaq is outdated and shouldn't be used to

Re: [ntp:questions] chrony as a server

On Thu, Feb 19, 2015 at 6:16 PM, Harlan Stenn wrote: > While that document is old and unmaintained > So put an appropriate note at the top of it and on the link to it from the WebHome page. No one that stumbles onto it is going to find any "gems". ___

Re: [ntp:questions] chrony as a server

On Thu, Feb 19, 2015 at 12:35 PM, David Taylor < david-tay...@blueyonder.co.uk.invalid> wrote: > Accurate and current documentation is both essential and invaluable for > any project! Well then under no circumstances should you read the ntp faq/howto at < http://www.ntp.org/ntpfaq/NTP-a-faq.htm>

Re: [ntp:questions] chrony as a server

On Thu, Feb 19, 2015 at 9:42 AM, Rob wrote: > > Ok but of course we are using PPS and a 16 second polling interval. > Use eight unless your system is broken in which replace it and then use eight. ___ questions mailing list questions@lists.ntp.org http

Re: [ntp:questions] chrony as a server

On Thu, Feb 19, 2015 at 5:34 AM, David Taylor < david-tay...@blueyonder.co.uk.invalid> wrote: > Does not NTP's orphan mode and local clock driver provide this? Refclock 1 (LOCAL/LOCL) is deprecated and I believe as of a recent release it's useless* but "Orphan mode is intended to replace the loc

Re: [ntp:questions] chrony as a server

On Wed, Feb 18, 2015 at 8:53 PM, William Unruh wrote: > On 2015-02-19, Paul wrote: > > On Wed, Feb 18, 2015 at 6:49 AM, Charles Elliott > > > wrote: > > > >> If you don't mind me asking, why is chrony superior to NTPD > >> for tracking a PPS si

Re: [ntp:questions] chrony as a server

On Wed, Feb 18, 2015 at 6:49 AM, Charles Elliott wrote: > If you don't mind me asking, why is chrony superior to NTPD > for tracking a PPS signal, or even in general Chrony (in general) pros and cons: < http://chrony.tuxfamily.org/manual.html#Other-time-synchronisation-packages> In the specif

Re: [ntp:questions] chrony as a server

On Mon, Feb 16, 2015 at 12:14 PM, David Taylor < david-tay...@blueyonder.co.uk.invalid> wrote: > I have a non-trivial interest I meant in Ntimed (the system) not time transfer in general. > If ntimed is not going to be available for Windows and OS/X that rules it > out for the great majority o

Re: [ntp:questions] chrony as a server

On Mon, Feb 16, 2015 at 2:57 AM, David Taylor < david-tay...@blueyonder.co.uk.invalid> wrote: > For me, there are two show-stoppers with Chrony: > > - no support for standard NTP monitoring commands. > > - no support for ref-clocks on Windows. > > Like many others, I have built up a considerable m

Re: [ntp:questions] chrony as a server

On Mon, Feb 16, 2015 at 5:22 AM, David Taylor < david-tay...@blueyonder.co.uk.invalid> wrote: > I hope that ntimed will not be available only on Linux If you have a non-trivial interest I suggest reading the notes. E.g. "Ntimed-client puts the entire interface to the OS timekeeping in four tri

Re: [ntp:questions] NTP offset doesn't change.

On Mon, Feb 16, 2015 at 1:11 AM, William Unruh wrote: > But that is not what you said. When I asked how ntimed works you > answered that it disciplines the computer clock. > BZZT! You said: "Be interesting to see how and what it does." To which I replied: "Since I've told you how it does an

Re: [ntp:questions] NTP offset doesn't change.

On Sun, Feb 15, 2015 at 1:18 PM, William Unruh wrote: > Thank you. I had no idea what the new version was called, and saw > someone call it timed. Sorry if it confused you. > This means you're not paying attention to details. It also means you're not reading PHK's notes. > I wanted YOUR summa

[ntp:questions] PHK on Ntimed and Chrony

I'm not completely convinced this is relevant to this list but I'm loath to paraphrase, restate, summarize or condense the Ntimed notes so quoting PHK < https://news.ycombinator.com/item?id=8781435>: "I'm not keen on saying too much about Chrony, I'd rather let people without a stake in the game p

Re: [ntp:questions] NTP offset doesn't change.

On Sat, Feb 14, 2015 at 11:21 PM, William Unruh wrote: > If you demand that I give > detailed explanation You started off down the ntpd versus chrony path again. "To get the discussion started, lets compare some of the differences between chrony and ntpd" That's not useful. You've spent year

Re: [ntp:questions] ambient temperature and it's effects on ref-ntpd (was NTP offset doesn't change.

On Sat, Feb 14, 2015 at 9:33 PM, Harlan Stenn wrote: > I have to wonder if it would be an appropriate GSoC project to > write something that monitors and tracks available temperature sensors > and correlates temperature (perhaps with the first derivative) with the > resulting effect on clock freq

Re: [ntp:questions] NTP offset doesn't change.

On Sat, Feb 14, 2015 at 6:38 PM, William Unruh wrote: > > When timed is actually out I may be interested in testing it again. > Ntimed-client. Again? So you've installed the code? < https://github.com/bsdphk/Ntimed> That seems unlikely. Read this:

Re: [ntp:questions] NTP offset doesn't change.

On Sat, Feb 14, 2015 at 2:09 PM, William Unruh wrote: > Because ntpd is what I know. Except you've admitted you don't know NTPd. > If you are saying that this is all up in the air again with > the new replacement, that would be great. But I have seen no evidence > thereof in discussions here.

Re: [ntp:questions] NTP offset doesn't change.

On Fri, Feb 13, 2015 at 8:48 PM, William Unruh wrote: > > > > I had a properly set up PPS source to do the comparison. > > As did I. > Ooops, I see that the text/plain part of the message was damaged. I was quoting you saying: " I had a properly set up PPS source" and my response was we have no

Re: [ntp:questions] NTP offset doesn't change.

On Fri, Feb 13, 2015 at 12:42 AM, William Unruh wrote: > OK, so we seem to have two different sets of experiments with very > different results. Note that I did not erase the drift file, or restart > ntpd after my perturbation. > Okay, I offset my clock by 100ms without restarting ntpd. It took

Re: [ntp:questions] NTP offset doesn't change.

On Thu, Feb 12, 2015 at 7:27 PM, William Unruh wrote: > It was based on measurements I made with ntpd > Are you assuming the numbers I provided are based on theory or were you looking over my shoulder when I perturbed system time by two milliseconds and watched it converge to O(10) microseconds

Re: [ntp:questions] NTP offset doesn't change.

On Thu, Feb 12, 2015 at 7:16 PM, William Unruh wrote: > Not really. But it should be distrubing that chrony disciplines clocks > much better ( lower jitter) than does ntpd in normal situations. Why? > And does that have lessons that ntpd could learn from? > If you don't stop fixating on NTPd you

Re: [ntp:questions] NTP offset doesn't change.

On Thu, Feb 12, 2015 at 12:00 PM, William Unruh wrote: > This means that if you are using say a PPS source, which gives > microsecond long term offset, it can take many hours to get there > This has been asserted and corrected before -- as in years ago*. A properly configured Linux system with

Re: [ntp:questions] NTP offset doesn't change.

On Thu, Feb 12, 2015 at 3:43 AM, William Unruh wrote: > It is hard to complain about a non-existant product. As has been previously mentioned ntimed(-client) is in early release. I've been running it since late December. ___ questions mailing list qu

Re: [ntp:questions] NTP offset doesn't change.

On Wed, Feb 11, 2015 at 4:32 PM, Harlan Stenn wrote: > There are times "repair" is perfectly acceptable, and we do that. > > There are times "replace" is better, and we do that. > My point is a long drawn-out discussion of changes to the core of ntp seem less than productive when the announced w

Re: [ntp:questions] NTP offset doesn't change.

On Wed, Feb 11, 2015 at 8:22 AM, brian utterback wrote: > But no one who does actively engage really understands > it or knows how to improve it. Unruh has a point, we don't know if there > isn't a better way built on statistical analysis. > > Since it seems the NTF "proposal" is to replace rathe

Re: [ntp:questions] leapseconds.list updates and ntpd

On Tue, Feb 10, 2015 at 12:19 PM, Harlan Stenn wrote: > No. The code looks for an updated file (daily, I think, more often as > we get closer to an expiration). > It checks every SECSPERDAY after start. I didn't notice any adjustments to the interval (leapf_timer) and the comment says daily. _

Re: [ntp:questions] Shared PPS source/Multiple PPS sources

On Sat, Feb 7, 2015 at 1:15 PM, William Unruh wrote: > Some receivers allow you to feed in the current location > Stationary (or fixed-position) operation is an expected capability of timing receivers. Likewise antenna delay, sawtooth correction if needed and loss of lock alarms. _

Re: [ntp:questions] Shared PPS source/Multiple PPS sources

On Fri, Feb 6, 2015 at 3:17 PM, wrote: > Ok, so these questions might be off the wall. > Yes. > > Is there any reason why I could not share the PPS output of say, my u-blox > 7 GPS module on multiple computers? Of course you can. However the correct way to do this is with a distribution am

Re: [ntp:questions] GPS Offset problems

On Mon, Feb 2, 2015 at 4:48 PM, wrote: > Back to the offset with the HP Z3801 and Z3805. This is not a leap second > bug, it is something I am doing wrong on the HP; I've got two Z3805s off by > 16 seconds They're using GPS rather tnan UTC time. Presumably some SCPI like this: :DIAG:GPS:UTC?

Re: [ntp:questions] GPS Offset problems

On Fri, Jan 30, 2015 at 8:09 PM, wrote: > Any idea what I am doing wrong? Probably nothing wrt the Datums. The 2100 has the "apply as soon as announced" leap second bug. There are some receivers. including the Z3812, that want to apply the leap second in March but the Z3801 is reported to be w

[ntp:questions] Trouble using refclock 18 (ACTS)

I have a USR 5637 connected to a Linux host using a VoIP line. I can manually dial and often* successfully connect to the NIST/USNO numbers. When used as a server it typically manages two (at random) successful connections over 8 polls. All other connection attempts fail including all other calls

Re: [ntp:questions] Timekeeping on Windows 2008r2 VM on Linux QEMU/KVM

On Thu, Jan 22, 2015 at 10:28 PM, Harlan Stenn wrote: > They are both reporting seconds. I'll change the subject on any further messages regarding sntp as a proper replacement for ntpdate. ___ questions mailing list questions@lists.ntp.org http://list

Re: [ntp:questions] Timekeeping on Windows 2008r2 VM on Linux QEMU/KVM

On Thu, Jan 22, 2015 at 4:07 AM, Rob wrote: > The problem is that ntpd believes that corrections it is applying are > because of frequency errors in the clock, while in this case they > are because of resets done externally. > > During the startup phase, bad things happen anyway (like touching th

Re: [ntp:questions] Timekeeping on Windows 2008r2 VM on Linux QEMU/KVM

On Wed, Jan 21, 2015 at 10:46 PM, Harlan Stenn wrote: > Right, so if you don't want that use sntp instead. > Are these numbers consistent? If ntpdate is reporting seconds and sntp is reporting milliseconds then it an order of magnitude difference. Otherwise it's several orders of magnitude. s

Re: [ntp:questions] Timekeeping on Windows 2008r2 VM on Linux QEMU/KVM

On Wed, Jan 21, 2015 at 10:17 PM, Harlan Stenn wrote: > > ntpdate -d > > That's covered. See > http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate > I may be abusing ntpdate but "ntpd -q -d (but sets the clock!)" is not the same as ntpdate -d which explicitly doesn't set the clock. > ntpdc

Re: [ntp:questions] Timekeeping on Windows 2008r2 VM on Linux QEMU/KVM

On Wed, Jan 21, 2015 at 5:40 PM, Harlan Stenn wrote: > ... I'm not aware of anything on either Windows or Unix that would cause > any > applied immediate adjustment to have *any* residual affect on ntp. > Well ... at least under Linux if ntpdate calls adjtime and then another program calls adjti

Re: [ntp:questions] Timekeeping on Windows 2008r2 VM on Linux QEMU/KVM

On Wed, Jan 21, 2015 at 6:00 PM, Mike Cook wrote: > I don't have a free client to test this on, but I believe that by > default ntpdate will SLEW the clock > Yes, even the most cursory grep of ntpdate shows adjtime and slewing. The -b and -B flags provide coarse controls. Unless you're a vic

Re: [ntp:questions] Timekeeping on Windows 2008r2 VM on Linux QEMU/KVM

On Wed, Jan 21, 2015 at 5:24 PM, Harlan Stenn wrote: > What is missing? We thought we caught all of the useful cases. > I made a small error. I meant ntpq and ntpd. ntpdate -d ntpdc fudge (admittedly that's not a query) ___ questions mailing list que

Re: [ntp:questions] Timekeeping on Windows 2008r2 VM on Linux QEMU/KVM

On Wed, Jan 21, 2015 at 9:48 AM, Sander Smeenk wrote: > What is actually wrong with running ntpdate to initially sync a clock? Nothing. The party line is that ntpdate and ntpdc are deprecated. I do hope that ntpq eventually incorporates all the features (I care about) of ntpdc and ntpdate bef

Re: [ntp:questions] Linux NTPd using a older Trimble Thunderbolt GPS Receiver

On Tue, Jan 20, 2015 at 1:45 PM, William Unruh wrote: > You would presumeably want a daemon to read the clock and toggle the pin, > perhaps with interrupts turned off That would be NTPd refclock 29 mode N where N select an event stamping receiver. Naturally doing this in user space increases

Re: [ntp:questions] Linux NTPd using a older Trimble Thunderbolt GPS Receiver

On Tue, Jan 20, 2015 at 6:51 AM, George Ross wrote: > From the Acutime 2000 user guide: "The time tag provides a resolution of > 320ns ...". Is PPS going to be sufficiently better that it would outweigh > the additional setup complexity? No. ___ ques

Re: [ntp:questions] I don't understand "Restrict" statements!

On Mon, Jan 19, 2015 at 4:55 AM, David Taylor < david-tay...@blueyonder.co.uk.invalid> wrote: > I get errors flagged at the points marked with "X" below: > Did you upgrade the version of NTPd? I don't think older versions checked for or cared about invalid keywords. > I've tried reading the do

Re: [ntp:questions] Leap second to be introduced in June

On Mon, Jan 19, 2015 at 10:43 AM, Mike S wrote: > Again, you need to up your understanding of standards terminology. > No, if you're going to use jargon you should provide the meanings you're using. Since you clearly have your own version of reality it will help the rest of us. > non-sequitur

Re: [ntp:questions] Leap second to be introduced in June

On Mon, Jan 19, 2015 at 9:56 AM, Mike S wrote: > You're citing a internal letter, from one BIPM group to another, asking > them to bring something before the ITU. It's not normative, it's not > informational, it's just correspondence. > That doesn't make any sense. When the ITU decides *not* do

Re: [ntp:questions] Linux NTPd using a older Trimble Thunderbolt GPS Receiver

On Mon, Jan 19, 2015 at 2:57 AM, George Ross wrote: > > Is there anyone with the prior experience in getting these older > > Trimble units to work? > > We've had a Trimble Acutime 2000 running since 2005, at two separate sites. > Although the Palisades driver has been extended to the Praecis, Th

Re: [ntp:questions] Leap second to be introduced in June

[And this is why I wonder why leap seconds are discussed here.] On Mon, Jan 19, 2015 at 7:15 AM, Mike S wrote: > You clearly misunderstood TF.460 > You're using the wrong reference. Try this one from 2007: which provid

Re: [ntp:questions] Linux NTPd using a older Trimble Thunderbolt GPS Receiver

On Fri, Jan 16, 2015 at 7:49 PM, Oceanos Admin 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 that will run unde

Re: [ntp:questions] Nice fanless high-perf NTP server: Fitlet!

On Fri, Jan 16, 2015 at 9:02 AM, Charles Elliott 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 can't send mail to no

Re: [ntp:questions] Nice fanless high-perf NTP server: Fitlet!

On Fri, Jan 16, 2015 at 2:02 AM, Terje Mathisen 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 case of client mode

Re: [ntp:questions] Nice fanless high-perf NTP server: Fitlet!

On Thu, Jan 15, 2015 at 9:23 PM, William Unruh wrote: > > This does give me the chance to ask what a high-perf NTP server might be. > I would have assumed the accuracy with which ntpd disciplines the computer > The jitter variability (from loopstats) on one of my clocks is ~1e-7, on another it's

Re: [ntp:questions] Nice fanless high-perf NTP server: Fitlet!

On Thu, Jan 15, 2015 at 4:40 PM, Terje Mathisen 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. This does give me the chance to ask what a high-perf NTP server might be. Given the constraints of

Re: [ntp:questions] Nice fanless high-perf NTP server: Fitlet!

On Thu, Jan 15, 2015 at 2:20 PM, David Taylor < david-tay...@blueyonder.co.uk.invalid> wrote: > .. although expensive compared to a Raspberry Pi, if somewhat better in > potential performance. > Among my (S1) clique of clocks the leading predictor of offset is network connection not cpu. As you m

Re: [ntp:questions] Nice fanless high-perf NTP server: Fitlet!

On Thu, Jan 15, 2015 at 1:16 PM, Rob wrote: > It was suggested as "a high-perf NTP server" > That string is not in the message. It's not a quote despite your quotation marks. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/list

Re: [ntp:questions] Nice fanless high-perf NTP server: Fitlet!

On Thu, Jan 15, 2015 at 12:03 PM, Rob wrote: > Terje Mathisen wrote: > > it would seem to > > be a nice NTPD startum 1 server. > > Of course, it could still be good enough when you want to use it as a > network time server. > Which is what was suggested. After all this is an NTP list not a hig

Re: [ntp:questions] Nice fanless high-perf NTP server: Fitlet!

On Thu, Jan 15, 2015 at 8:41 AM, Terje Mathisen wrote: > [Fitlet] includes a serial port which should make it trivial to attach a > Sure GPS board. > If they use a standard pinout. The PC-2i didn't support DCD which makes it not quite trivial. Hopefully the hardware documents will be released s

Re: [ntp:questions] Leap second to be introduced in June

On Wed, Jan 14, 2015 at 5:00 AM, Terje Mathisen wrote: > By _far_ the largest majority of all system time calls are asking for the > _current_ time, right? Are there (common) systems that have kernel calls for other than the current time? ___ questio

Re: [ntp:questions] NTP 4.2.8 for Windows, not branded

On Mon, Jan 12, 2015 at 10:58 AM, Danny Mayer wrote: > None of these are valid nor are they for you to use. Take down the mailing list/Usenet gateway. Or make it smarter. I would vote for the former. ___ questions mailing list questions@lists.ntp.org

Re: [ntp:questions] Leap second to be introduced in June

On Mon, Jan 12, 2015 at 12:46 AM, Mike Cook wrote: > > Why do folks mention leap seconds on this list? > part of the NTP protocol deals with the scheduling insertion/deletion of > leap seconds. > I should have phrased that differently. Or just let it go. > > > Why do people point to leap-s

Re: [ntp:questions] Leap second to be introduced in June

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 > cod

  1   2   3   4   >