On 24/06/2022 11:26, Harlan Stenn wrote:
I chatted with him a couple of months' ago. He's doing OK.
Thanks, that's good to hear. He did a lot of work, which was much appreciated.
Cheers,
David
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email:
On 23/06/2022 15:33, Thibaut HUMBERT wrote:
Hi David!
I tested with your dll:
https://www.satsignal.eu/ntp/x86/loopback-ppsapi-provider.zip
The PPS was not detected, I don't know what I did wrong.
Here is the content of my ntp.conf:
server 127.127.20.3 minpoll 2 maxpoll 2 mode 89 prefer
fudge
On 22/06/2022 22:42, Thibaut HUMBERT wrote:
I continued my tests with the NMEA+PPS on a CH341A in USB, and comparing over
one night with several NTP sources: I am at ± 1ms on average.
I tried with an ESP8266: without success.
I tried a Raspberry PI 1B: ok, but always an 10ms offset. And the
On 17/06/2022 03:03, Daniel O'Connor wrote:
Yes, Thiebaud, USB is not good enough for PPS signals!
This is absolutely false.
If you are using it for NTP then GPS+PPS over USB is quite adequate (from
personal experience).
Ian Lepore (RIP) who worked for Micro Semi and worked on FreeBSD did a
On 16/06/2022 10:00, Thiebaud HUMBERT wrote:
To do the inversion, I just changed the "Pulse Mode" parameter to "Falling edge" from
"Rising edge".
The offset induced by the "pulse length" has disappeared.
But there is still an offset of around 10.3ms, which I think is induced by USB
as
On 10/06/2022 11:15, David Woolley wrote:
On 10/06/2022 08:47, joshua wrote:
connect to the right timezone
NTP doesn't use timezones. All servers use times based on UTC. Any
timezone issue is a local problem, in your operating system.
Maybe he means the zone for the pool servers, but
On 10/06/2022 08:47, joshua wrote:
As title states, we've been unable to connect to the right timezone without
doing it manually. I was wondering if anybody has been having these problems?
I have already tried to change the server to the Dutch server with no succes..
The times are now so far
On 26/06/2021 07:58, Derek Barnes wrote:
Thanks David.
sudo yum remove chronygets rid of chrony and 62 dependencies but sudo
install ntp fails. (Error: Unable to find a match: ntp)
I believe /assume that there is no ntp packages in the centos8 repositories.
Can my installation be
On 26/06/2021 05:45, Derek Barnes wrote:
I have recently built a server running Centos8 only to find that it doesnot
support ntpd, only chronyd.
That would not be a problem except that chrony does not like my stratum 1 GPS
receiver and the only possible reason that I can work out is the
On 29/01/2021 10:33, Fabbri, Tommaso CMRE wrote:
Dear NTP users,
which is the difference between loopstats and peerstats for evaluating the
drift respect a given timing source?
In my configuration, the NTP server is configured with just one additional
source (GPS) always available.
Should
On 25/01/2021 16:33, Jim Pennino wrote:
[]
But the PPS has a lot of jitter. Note the xPPS(0) in the ntpq line.
[]> The default for NTP is 4800 baud, but I am running at 9600 and there is
no loss of data.
It doesn't make any difference if I run the 20 driver in mode 1 (lower
bits) or 13, it
On 25/01/2021 17:53, Gary E. Miller wrote:
Yo David!
On Mon, 25 Jan 2021 11:03:46 +
David Taylor wrote:
GPSD has proved problematical, and the only satisfactory way is not to
use the one in the distribution, but to build from scratch.
https://www.satsignal.eu/raspberry-pi
On 25/01/2021 02:06, Jim Pennino wrote:
I got a Pi 4 and Adafruit ultimate gps hat to play with and decided to see
how good it was as a timekeeper.
First weird thing; xgps does not show a skyview but both xgps and cgps
show at least 10 satellites in use.
I don't care too much about this one as
On 19/01/2021 20:04, Martin Burnicki wrote:
Maybe have a look at this page:
http://doc.ntp.org/current-stable/drivers/driver28.html
Search that page for "flag1". There should be 2 hits about a constraint
in the initial time offset ("Mode-independent post-processing"), and how
this can be
NTP doesn't work as expected when using PPS and GPSD alone, when there
is a very large offset (2 years) between the host date/time (Raspberry
Pi) and the GPS date/time. PPS and GPSD appear to be present (using
"ppstest" and "ps-e | grep gpsd", and the ntpq display shows the PPS and
GPS servers
On 24/11/2020 04:05, Scott wrote:
Hi all,
the documentation clearly states that for a PPS driver to work one needs to
configure another peer as `prefer'.
I have a set-up with PPS and three network (IP) peers, one of these marked
preferred.
1) why can't the PPS signal be used to discipline all
On 14/09/2020 13:45, Rob van der Putten wrote:
Hi there
On 24/08/2020 16:07, William Unruh wrote:
It was renamed because UTC has nothing to do with Greenwich. For
historical reasons, the time at Greenwich is the same as UTC.
They are not perfectly identical. The difference is however
On 21/08/2020 12:01, thimoo...@gmail.com wrote:
Op vrijdag 21 augustus 2020 om 12:52:49 UTC+2 schreef David Taylor:
On 21/08/2020 11:39, thimoo...@gmail.com wrote:
I have a question. how do you make a graph of your ntp server and is that
possible
i need a linux version
The tools I use
On 21/08/2020 11:39, thimoo...@gmail.com wrote:
I have a question. how do you make a graph of your ntp server and is that
possible
One example is here:
https://www.satsignal.eu/ntp/NTPandMRTG.html
--
Cheers,
David
Web: http://www.satsignal.eu
On 17/06/2020 00:03, William Unruh wrote:
Unless the cables are properly terminated at boththe gps receiver and
the computer, this is probably not true. (the velocity of light may be
under 5ns (ie less than 5 feet between the receiver and the computer)
but the capacitive charging of the cable,
On 16/06/2020 17:11, William Unruh wrote:
[]
The question then is how rapidly the system can respond to an
interrupt,. This at least used to be of the order of a microsecond.
Also, how logd does it take to read the clock with the kernel gettime
routines. They all limit the accuracy of your clock
Forgot the link:
RasPi-1: https://www.satsignal.eu/mrtg/performance_raspi-1.php
--
Cheers,
David
Web: http://www.satsignal.eu
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On 16/06/2020 14:04, Miroslav Lichvar wrote:
On 2020-06-16, David Taylor wrote:
The clock on a Raspberry Pi ranges from 700 to 1500 MHz, so clock
resolution is in the nanosecond range.
For best timekeeping performance, you would want to set the CPU
frequency to a fixed value.
I would also
On 15/06/2020 19:00, David Woolley wrote:
[]
What is the clock resolution? If you try and measure jitters that
aren't several times the resolution, they are not going to be
particularly valid.
If the hardware clock is almost dead on, and the peak to peak dither is
just less than the
On 15/06/2020 19:58, William Unruh wrote:
[]
Why would it be useful? What are you trying to do. It is always better
to first present the problem rather than trying to get people to improve
your solution to an unknown problem.
It's not a problem, simply trying to get a better understanding of
On 15/06/2020 19:53, William Unruh wrote:
[]
And why would you think that posting it to the newsgroup would get the
people in charge of the email list?
Do you mean one of the mailing lists listed on
https://lists.ntp.org/listinfo? Which one?
There it says
If you are having trouble using the
On 15/06/2020 16:10, Miroslav Lichvar wrote:
On 2020-06-15, David Taylor wrote:
[]
The lightly-loaded Raspberry Pi cards are all showing low numbers of
jitter, and it would be really useful to get that in more than three
decimal places of milliseconds.
You would probably need to patch ntpd
On 15/06/2020 08:33, Miroslav Lichvar wrote:
On 2020-06-14, David Taylor wrote:
When using the ntpq -crv command, which is the better measure of system
performance - clk_jitter or sys_jitter? I've look for the definitions
and I'm thinking sys_jitter but perhaps someone could please remind me
On 15/06/2020 14:50, William Unruh wrote:
On 2020-06-15, David Taylor wrote:
Once again, I tried to reply on the e-mail link but the message was
rejected, Could the mailing list admin please set it so that:
No idea what you wanted to do. If you wanted to reply to the poster's
email
Once again, I tried to reply on the e-mail link but the message was
rejected, Could the mailing list admin please set it so that:
david-tay...@blueyonder.co.uk
gm8...@yahoo.co.uk
are allowed through, please. This hindrance to communication is most
tirecome!
--
Cheers,
David
Web:
When using the ntpq -crv command, which is the better measure of system
performance - clk_jitter or sys_jitter? I've look for the definitions
and I'm thinking sys_jitter but perhaps someone could please remind me
of the difference?
Are the units for sys/clk_jitter in milliseconds. For my
On 21/08/2019 21:01, David Woolley wrote:
On 21/08/2019 17:42, David Taylor wrote:
You are not allowed to post to this mailing list From: a domain which
publishes a DMARC policy of reject or quarantine,
blueyonder doesn't appear to publish any DMARC policy. Did you actually
use a blueyonder
Trying to reply to an NTP Questions request I get this:
You are not allowed to post to this mailing list From: a domain which
publishes a DMARC policy of reject or quarantine, and your message has
been automatically rejected. If you think that your
On 16/07/2019 21:19, Andreas Mattheiss wrote:
Hello,
I have a cheap GPS hooked onto my PC via a MAX232 level converter - the
PPS goes directly into the DCD pin of a native serial port.
Everything is fine; after some time ntpd locks onto the PPS signal, and
any other servers from the net show a
On 10/07/2019 22:15, Michael Haardt wrote:
I use a Garmin LVC 18x with a Raspberry Pi, process NMEA with gpsd
(SHM driver) and acess PPS by GPIO (kernel PPS driver). gpsd allows
monitoring and passing PPS right into ntpd avoids gpsd conversion of PPS.
Sometimes this works, but then there are
On 03/07/2019 10:52, Roger wrote:
On Wed, 3 Jul 2019 00:56:08 -0700 (PDT), rickylje...@gmail.com
wrote:
Server 206.108.0.131 which is part of 0.pool.ntp.org is returning a date and
time that is off around 11 hours. Trying to find any details of why this would
be happening.
The change was
On 25/06/2019 01:33, Chris wrote:
[]
Thanks for all the replies. I guess the next thing to do is to build
a working system, then evaluate to see how it can be improved. All
the kit is in the same rack and with dedicated hardware interfaces,
network latency shouldn't be a problem. This is
On 27/04/2019 23:29, jelisko...@gmail.com wrote:
[]
I am thinking of buying this
https://www.ebay.com/itm/U-Blox-LEA-5T-high-precision-timing-GPS-module-dev-board-1PPS-USB-RS232-ntp-ser/263546760982
With this antenna
On 27/04/2019 17:37, William Unruh wrote:
[]
On the subject of gps/pps receivers, since the Sure OEM board seems to
have disappeared, what is the current recommendation for a cheap gps/pps
board to attach to your computer? (the above is not cheap-- on the
order of $500, rather than $50)
On 26/04/2019 18:39, William Unruh wrote:
[]
One problem with the pool is that the servers have varying accuracy. If
you have carefully chosen your servers as having low uncertainty, then
your list might be better. But if you simply chose them randomly, then
the pool will probably be just as
On 26/04/2019 21:27, jelisko...@gmail.com wrote:
[]
I think that you are mistaken.
" The servers joining should not have pool.ntp.org as their upstream server(s), but
should configure some good servers manually (those servers may be chosen from the pool.
The point is that they are chosen
On 26/04/2019 14:31, jelisko...@gmail.com wrote:
Hi guys,
This is my config file for my NTP Stratum 2 server. Any suggestion for fine
tuning will be appreciated.
[]
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
On 12/09/2018 08:06, Jakob Bohm wrote:
NTP 4.2.8p10+dfsg-3+deb9u2 (Debian packaged with backported security
fixes), on a dual stack (IPv4+IPv6) machine logs the following error
messages for each netmask specific restrict line, and does seem to
ignore the lines or otherwise enforce incorrect
There has been an update to NTP to ntp-4.2.8p12 and I've compiled a
version for Windows (XP up to Win-10-32/64) here:
http://www.satsignal.eu/ntp/x86/index.html
Note that you might need to update your OpenSSL too, details on that Web
page. Thanks to @NTP for the update.
--
Cheers,
David
On 10/08/2018 23:16, na...@datacloud.com wrote:
I forgot to mention that I am using Ubuntu 16.04 and the GPS receiver is
connected via USB
USB is not the best to get good results. You need to connect the PPS
signal directly to a port on the device - typically the CD (carrier
detect) line
On 11/08/2018 12:29, Terje Mathisen wrote:
David Taylor wrote:
This was posted by lu...@fridolin.com on the NTP hackers list, just
in case you missed it.
~ Hi,
I've been writing a reference driver for u-blox GPS receivers as
part of my master's thesis
This was posted by lu...@fridolin.com on the NTP hackers list, just in
case you missed it.
~
Hi,
I've been writing a reference driver for u-blox GPS receivers as part
of my master's thesis and thought ntp hackers might be interested in it.
On 02/08/2018 09:14, David Woolley wrote:
On 01/08/18 19:32, David Taylor wrote:
Would I be right in thinking of the "*" line as simply being the
offset from that particular server, and the "system" variable as being
the offset from some virtual internal clock which
I was writing a small script to check on offset, and noticed that the
offset from the selected server ("*" line in the tally list from ntpq
-p) differs considerably from the offset reported as a "system" variable
(ntpq -crv).
Would I be right in thinking of the "*" line as simply being the
Angelo Mileto recently sent me some notes about determining the offset
of serial GPS data automatically using a Linux script. This value is
used as the time1 fudge factor. I hope you find it useful. My thanks
to Angelo!
https://www.satsignal.eu/ntp/Raspberry-Pi-NTP.html#average
--
Cheers,
On 05/07/2018 21:30, Daniel Gearty wrote:
server 127.127.20.3 iburst minpoll 3 mode 17
# COM3, 8 second polling, NMEA GPRMC, 9600 bps, NaviSys GR-8013W u-blox M8 USB
PPS GPS
fudge 127.127.20.3 time1 0.000142 time2 0.11 flag1 1 flag2 1 flag3 0
# PPS offset, NMEA offset, enable PPS, pulse on
On 07/07/2018 18:10, William Unruh wrote:
On 2018-07-07, David Taylor wrote:
[]
On one PC I'm using an add-in PCIe card, a TTL-RS232 converter (tried
without but the signal levels were too low) and a Chinese module sitting
That is really unusual. Most serial cards now will happily use TTL
On 06/07/2018 21:18, Daniel Gearty wrote:
In my case, I attribute the PPS delay to the serial to USB 1.1 conversion of
the Prolific PL2303HXD in my NaviSys GR-8013W GPS. The offset bounces around
within +/- 0.5 msec.
It appears the initial PPS offset should be zero if you receive your PPS
On 04/04/2018 20:47, Maria Iano wrote:
Thanks William, I will go with GPS.
Maria
That's a good choice. These boxes are low-cost (but not yet multiple
GNSS systems - check with the vendor), and have good hold-over in the
event of GPS failure:
On 04/04/2018 17:29, Maria Iano wrote:
I'm purchasing ntp appliances to put into three datacenters. Does it make sense
to purchase two that use GPS and two that use WWVB, and configure them as peers?
Thanks,
Maria
Probably, yes, although these days I would suggest that GPS (including
GLONASS
On 28/03/2018 21:31, Yves Martin wrote:
I've installed my own ntp server since a year now, using a NTP100 server sync
with an external GPS antenna. Just need to know if it's reachable from outside.
Thanks.
ntp.ymartin.com
YM
Yves, this is what I see (edited for brevity):
Folks,
There has been an update to NTP to ntp-4.2.8p11 and I've compiled a
version for Windows (XP up to Win-10-32/64) here:
http://www.satsignal.eu/ntp/x86/index.html
Note that you may need to update your OpenSSL too, details on that Web
page. Thanks to @NTP for the update and to Juergen
On 19/11/2017 06:29, William Unruh wrote:
[]> t but it is annoying to keep seeing 8 or more postings
only to have all of them killed. It is bizzare, and wonder if there is some
way of getting google to kill that account.
Can you check other devices in the same location? I've seen something
On 18/11/2017 21:55, William Unruh wrote:
I am having sudden problems on my system with a Sure GPS with PPS.
I am running chrony, using a serial port to bring in the PPS signal.
Everything was working well-- the rms timing on the pulse was about 1usec.
Suddenly on Nov 18 at very close to
On 03/11/2017 00:23, Geoff Roberts wrote:
Never mind. I found it. Nice 64 bit signed Kernel mode version too.
http://www.satsignal.eu/ntp/NTP-on-Windows-Vista.html#Win-7-64-bit
Haven't tried it on win10 yet but should work.
Geoff
Yes, the driver works on Windows-10. If you have a
On 01/11/2017 11:46, valizadeh...@gmail.com wrote:
[]> local lcok is there because my system is not connected to internet
and i need to have the hwclock to keep the time during power-offs,i have
disabled the pre installed fakeclock and used an I2c connected battery
backed up RTC chip.
the
On 31/10/2017 08:50, valizade...@gmail.com wrote:
server 127.127.1.1 minpoll 3 maxpoll 4 #hwcloak
fudge 127.127.1.1 stratum 3
As Bill says, get rid of the local clock, and add some Internet sources.
That way you can check whether your GPS is grossly wrong. The reach
value seem wrong as
Hi,
Perhaps the problem comes from the first line when it's asked:
restrict source ... query
It is possible that the word 'query' is not recognize, usually 'restrict'
command is used to disable services and not to enable them.
Best,
Jean-Michel
Thanks Jean-Michel and Harlan.
Yes, both the
Folks,
I will be the first to admit that I'm not very conversant with
"restrict" lines, so perhaps the following will be obvious to you! I
have in lines 34 onwards of my ntp.conf:
# Suggestions for NTP restrictions:
restrict source notrap nomodify nopeer query
restrict 127.0.0.1
restrict
On 06/06/2017 13:11, girin...@gmail.com wrote:
[]
Some GPS will continue to deliver a PPS signal even if the lock is lost. I'm
thinking particularly about the Garmin 18xLVC where it is clearly indicated in
the documentation (4.4.1): 'After the initial position fix has been calculated,
the PPS
On 05/06/2017 22:53, Jakob Bohm wrote:
[]
Note that any failure in the GPS/GNSS radio hardware that actually
provides both the PPS pulses and the NMEA messages would be a failure of
both "ntpd sources".
Thus such a failure of NMEA+PPS would be more common than a failure of
NMEA or PPS alone.
On 26/05/2017 12:59, gaurav10ni...@gmail.com wrote:
[]> Hi David,
I want to get offset between 0.5-2 ms. Can it be achieved using meinberg
application?
If yes, Kindly share the parameters required to be changed to get offset value
in the required range.
Regards,
Gaurav
Gaurav,
As with
On 12/05/2017 06:33, Jakob Bohm wrote:
[]
Note that all recent/current versions of the Windows Time Service are
in fact SNTP/NTP implementations, with quality of implementation
improving in newer versions.
Old (now unsupported) versions of the Windows Time Service violated the
SNTP/NTP
On 07/04/2017 08:33, seema pandhre wrote:
On Wednesday, March 22, 2017 at 6:57:36 PM UTC+5:30, David Taylor wrote:
NTP 4.2.8p10 released
Windows binaries working on Windows-XP SP3 & later - download:
http://www.satsignal.eu/ntp/x86/index.html
Source: http://archive.ntp.org/ntp4/ntp-4.2
On 27/03/2017 22:34, Dan Gearty wrote:
Hi David, that is interesting that the problem does not manifest across the
board given Martin's description of the bug.
I am using the Meinberg build on Windows 10 Pro.
I had previously been depending upon the environment variable.
On 25/03/2017 22:09, Dan Gearty wrote:
I have been using the loopback driver on Windows 10.
It had been running OK in older versions up to 4.2.8p9.
Now in 4.2.8p10 it appears that junk characters are appended to the driver
name when it is called. The junk characters are different each time NTP
NTP 4.2.8p10 released
Windows binaries working on Windows-XP SP3 & later - download:
http://www.satsignal.eu/ntp/x86/index.html
Source: http://archive.ntp.org/ntp4/ntp-4.2/ntp-4.2.8p10.tar.gz
--
Cheers,
David
Web: http://www.satsignal.eu
___
On 05/02/2017 00:22, Robert Scott wrote:
[]
By the way, the code I am writing is not part of a NTP algorithm to
adjust a system clock for time. It is for a one-time frequency
calibration of an oscillator. I take a time snapshot at the beginning
and at the end of an approximately six hour
On 03/02/2017 07:42, sean wrote:
[]
Just curious, any experience with those?
[]
I'm running a couple of Sure boards here one feeding one PC and the
other feeding two PCs in parallel (only one PC has TX connected). No
problems. I'm on the top storey of a two storey building, and both
On 02/02/2017 04:34, sean wrote:
[]
Incidentally I do have a BBB and a few raspberry pis. The BBB goes back
and forth to/from work so I won't be able to use that as the NTP host.
As an aside, have you done anything with SDR? You may be interested in
this:
https://github.com/flightaware/piaware
On 01/02/2017 10:59, Jakob Bohm wrote:
[]
As I am looking at the BBB myself, here are some extra questions:
1. Do you know if anyone has tried using the real-time coprocessors on
the BBB to more accurately track the PPS signal?
2. I presume the BBB could be put in a shielded case (I see some
On 01/02/2017 05:55, sean wrote:
[]
Hi Dave,
Thank you for the reply. I found your website about 3 weeks ago and got
the urge to checkout GPS devices, like the GPS18, Raspberry pi options,
etc. Thank you for it and all of the graphs. You certainly have many Pis
keep track of the time! I don't
On 31/01/2017 23:35, Phil Lee wrote:
[]
That would be correct IF your LAN is on 192.168.0.n
The zero should be replaced with whichever of the /24 subnets under
192.168 is relevant for the actual LAN address scheme. Some DHCP
servers on routers default to 192.168.1.n, for example.
[]
Well, of
On 30/01/2017 20:14, Antonio Marcheselli wrote:
Hello all
[First, I am using google groups, in the past I was told it was causing hassle
in terms of formatting but BT have discontinued their news server and I am
unable to find an alternative - apologies if these messages are not properly
On 30/01/2017 04:13, sean wrote:
Hi All,
I'm real interested in NTP and accurate time, hence why I'm on this
newsgroup. I would like to look into getting a time sensor and I hear
the Garmin GPS 18X is what some folks run unless they need much more
precision. Is this still a pretty well
On 07/03/2015 08:35, catherine.wei1...@gmail.com wrote:
[]
Hi,Dayvid, just like you said, we're offering ntpq to our customers to test the
ntp function, for example, they have sevral ntp servers and need to choose
which servers are good, they need to switch between these servers. Thank you.
On 07/03/2015 12:41, Neil Green wrote:
In an attempt to squeeze all I can out of a NTP and GPS/PPS setup on the
Raspberry Pi 2 I’m starting to experiment with compile flags using GCC 4.8.
Currently I have:
CC=gcc-4.8 CFLAGS=-mcpu=cortex-a7 -mfpu=neon-vfpv4 ./configure
--enable-NMEA
On 07/03/2015 11:12, Harlan Stenn wrote:
OK, a fair amount of good stuff is being discussed.
Do we mostly all agree that the purpose of the drift file is to give
ntpd a hint as to the frequency drift at startup?
If so...
The current mechanism is designed to handle the case where ntpd is
On 06/03/2015 09:35, Harlan Stenn wrote:
Folks,
A while ago we got a request from the embedded folks asking for a way to
limit the writing of the drift file unless there was a big enough
change in the value to warrant this.
Somebody came up with an interesting way to do this that involves
On 02/03/2015 09:30, catherine.wei1...@gmail.com wrote:
Hi,David,
In our system, we need to unconfig and restrict in some operations through ntpq
utility which originally was realized by ntpdc. However, ntpdc doesn't work
now. In other words, we need to find an equivalent of ntpdc to unconfig,
On 28/02/2015 01:17, catherine.wei1...@gmail.com wrote:
[]
Hi, Harlan
In my system, ntpdc was used to add an ntp server and the command is like this:
ntpdc -c keyid 0 -c addserver 10.172.161.16 minpoll 3 maxpoll 4 burst
since keyid is 0, we don't need authentication. But now, I use ntpq to
On 21/02/2015 19:00, Harlan Stenn wrote:
David Taylor writes:
[]
http://www.satsignal.eu/ntp/Raspberry-Pi-quickstart.html
http://www.satsignal.eu/ntp/Raspberry-Pi-NTP.html
Yes, that is appropriate material for the site. There are already pages
for how to build for certain other
On 21/02/2015 08:33, Mike Cook wrote:
[]
My aged understanding concurs with yours. Set flag 1. Maybe not your
desired behavior, but possibly that of the designer.
[]
Thanks, Mike. We are carrying out some tests, but it means leaving the
computer down for at least several hours, and
On 21/02/2015 11:40, Harlan Stenn wrote:
David Taylor writes:
Thanks, Mike. We are carrying out some tests, but it means leaving the
computer down for at least several hours, and we've been trying about 24
hours down so far, so progress isn't rapid! If flag1 allows
off-the-network operation
On 21/02/2015 17:52, William Unruh wrote:
[]
It will do that too. The crucial item there is the only method of time
correction is manual entry which is different from ntpd and orphan
mode. I have no idea why this conversation is continuing. The two are
different. The two methods are trying to
On 20/02/2015 20:22, William Unruh wrote:
[]
No. The local clock simply trusts the time (Ie all offsets are defined
to be zero) chrony takes the time as entered by hand by the operator and
uses that to determine the offset. Of course that will not be terribly
accurate ( a second is probably
Folks,
I'm looking at:
http://www.eecis.udel.edu/~mills/ntp/html/drivers/driver28.html
and wanting to be sure that I understand flag1 correctly. The situation
is starting a computer which has no real-time clock, and has been down
for a day. This computer is in the middle of nowhere, and
On 21/02/2015 07:04, William Unruh wrote:
[]
orphan mode is about a group of computers. Orphan Mode allows a group
of ntpd processes to automonously select a leader in the event that all
real time sources become unreachable (i.e. are inaccessible).
chrony's is that you can enter the time by
On 19/02/2015 18:09, Paul wrote:
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
On 19/02/2015 01:24, Paul wrote:
[]
Chrony (in general) pros and cons:
http://chrony.tuxfamily.org/manual.html#Other-time-synchronisation-packages
[]
... whwre it says: Things chronyd can do that ntpd can’t: chronyd
provides support for isolated networks whether the only method of time
On 19/02/2015 14:20, Paul wrote:
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
On 16/02/2015 19:54, Paul wrote:
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
On 16/02/2015 15:59, Paul wrote:
[]
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
trivial functions for portability, but there are other nits and downright
idiotic incompatibilities, because, quite
On 16/02/2015 08:46, William Unruh wrote:
[]
I think, but am not sure, that the biggest problem with porting chrony
to windows is that windows does not have a good way of having the kernel
discipline the clock-- the equivalent of adjtimex on Linux.
NTP already manages that very well on
On 15/02/2015 22:40, Rob wrote:
I am experimenting with chrony 1.31 as an alternative on some PPS
synchronized servers. It appears to run OK, it is tracking very nicely:
[]
For me, there are two show-stoppers with Chrony:
- no support for standard NTP monitoring commands.
- no support for
1 - 100 of 645 matches
Mail list logo
