On 13/08/2013 23:03, Charles Swiger wrote:
Hi--
[]
I wonder how many of the Windows users do anything with ntpd which needs crypto?
ntpd by itself (ie, ./configure --without-crypto) has a fairly clean
security history compared to something like OpenSSL's ASN.1 parser:
On 13/08/2013 22:41, Harlan Stenn wrote:
David Taylor writes:
On 13/08/2013 21:23, Danny Mayer wrote:
[]
All binaries need to be built together with the same versions. You
should not be mixing binaries.
Danny
Thanks, Danny. Perhaps,ideally, but in that case, why are the SSL
sources not in
David Malone wrote:
It seems my ancient GPSclock 200 has recently slipped back to
December 1993 too. Resetting it hasn't helped and I doubt I will
be able to do a firmware update, so I've made a hack to refclock_nmea.c
(version ntp-4.2.6p5), by replacing:
reftime.l_ui +=
Terje Mathisen terje.mathisen at tmsw.no writes:
Nice!
You've replaced the 1024-week epoch with a +/- 512-week window around
the current time. :-)
Indeed - ntp already sort of has to do a similar, because the
timestamps are mod 2^32 seconds from 1900, so using a trick like
this is only
On 2013-08-14, Mark C. Stephens ma...@non-stop.com.au wrote:
Good on you David and welcome back to 2013.
I do hope that some official changes are made to refclock_nmea to catch this
receiver bug and process it accordingly.
There are a lot of folks stranded in 1993.
--marki
-Original
Um Let's see, Datum was bought by Austron, who was bought by ... etc.
For collectors such as myself, having this 'mature' equipment still working is
great.
Looking at Mr Malone's code, he added 2 lines which enabled NTPD compatibility
with GPS receivers that would have long ago have been sent
For ntpd 4.2.4p6 running on Linux, is there any significance to the order
of servers in the ntp.conf file? Will ntpd synchronize with the first
available/good time server in the list?
Thanks,
Nils Brubaker
___
questions mailing list
On 2013-08-13, Nils Brubaker n...@us.ibm.com wrote:
For ntpd 4.2.4p6 running on Linux, is there any significance to the order
of servers in the ntp.conf file? Will ntpd synchronize with the first
available/good time server in the list?
No, no.
ntp gets the data from all the servers. It then
Mark C. Stephens ma...@non-stop.com.au wrote:
Um Let's see, Datum was bought by Austron, who was bought by ... etc.
For collectors such as myself, having this 'mature' equipment still working
is great.
Looking at Mr Malone's code, he added 2 lines which enabled NTPD
compatibility with GPS
Thank you, un...@invalid.ca, for your response to my question.
Couple follow-up questions. My ntp.conf running on Linux has 4 servers
defined:
server 0.rhel.pool.ntp.org
server 1.rhel.pool.ntp.org
server 2.rhel.pool.ntp.org
These are public servers from the NTP pool project. In my
On 13/08/2013 20:52, Nils Brubaker wrote:
For ntpd 4.2.4p6 running on Linux, is there any significance to the order
of servers in the ntp.conf file? Will ntpd synchronize with the first
available/good time server in the list?
Thanks,
Nils Brubaker
The order you list likely determines the
I don't understand how you get the idea that your system is
synchronizing with only one server when the messages you posted show it
synchronizing with 6 servers. Do you mean that it is synchronizing with
one server at a time? That is what it is supposed to do. There is a
combining step in the
On 14/08/2013 12:54, unruh wrote:
[]
Except of course if the rd_timestamp.l_i is way out (that is why one
would want to use a gps clock to fix it-- eg on bootup with the
Raspberry Pi say),
[]
Could you not use something like the timestamp of some file (e.g. the
drift file) or other system
David Taylor david-tay...@blueyonder.co.uk.invalid writes:
Could you not use something like the timestamp of some file (e.g. the
drift file) or other system file to get the approximate year? I haven't
studied the code (I find C not easy to read or navigate) so perhaps it
already does this.
On 14/08/2013 17:14, David Malone wrote:
[]
Possibly - this was a handy timestamp to use, but there may be a
better choice. It's also possible that this should be an optional
flag to the driver, so that people with perfectly good GPS units
won't ever trip over the code ;-)
David.
Yes,
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 14/08/2013 17:14, David Malone wrote:
[]
Possibly - this was a handy timestamp to use, but there may be a
better choice. It's also possible that this should be an optional
flag to the driver, so that people with perfectly good GPS
On 2013-08-14, Nils Brubaker n...@us.ibm.com wrote:
Thank you, un...@invalid.ca, for your response to my question.
Couple follow-up questions. My ntp.conf running on Linux has 4 servers
defined:
server 0.rhel.pool.ntp.org
server 1.rhel.pool.ntp.org
server 2.rhel.pool.ntp.org
These are
On 2013-08-14, David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 14/08/2013 12:54, unruh wrote:
[]
Except of course if the rd_timestamp.l_i is way out (that is why one
would want to use a gps clock to fix it-- eg on bootup with the
Raspberry Pi say),
[]
Could you not use
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 14/08/2013 12:54, unruh wrote:
[]
Except of course if the rd_timestamp.l_i is way out (that is why one
would want to use a gps clock to fix it-- eg on bootup with the
Raspberry Pi say),
[]
Could you not use something like the
David Malone writes:
Indeed - you need to have a timestamp within about ten years of
correct before you start up, otherwise the problem will be worse. Ntp
has the same problem in figuring out the ntp epoch, though we've yet
to see an ntp timestamp wrap around.
ntp-dev has a fix for this
On 2013-08-14, unruh un...@invalid.ca wrote:
On 2013-08-14, Nils Brubaker n...@us.ibm.com wrote:
Aug 8 15:01:00 yellowstone ntpd[3254]: synchronized to 50.116.55.161,
stratum 2
Aug 8 16:09:20 yellowstone ntpd[3254]: synchronized to 38.101.77.21,
stratum 2
These log messages suggest
Charles Swiger wrote:
I wonder how many of the Windows users do anything
with ntpd which needs crypto?
(Shrug)
http://www.eecis.udel.edu/~mills/ntp/html/manyopt.html#mcst
I use ntpd with MD5 symmetric keys for manycast
on all clients / servers.
...
keys /etc/ntp.keys # e.g. contains: 123
Harlan Stenn wrote: ntp-dev has a fix for this problem - while the original
solution was make sure the clock is correct to within
~65 years' time the new code uses a date of compile value,
and needs the system time to be either 10 years' before
that date or up to 128 years' after that
Mark C. Stephens wrote:
remote refid st t when poll reach delay offset jitter
===
oPPS(0) .PPS. 0 l- 16 377 0.000 -0.001 0.004
*GPS_PALISADE(0) .GPS. 0 l 16 16 377 0.000 0.018
Hi,
On 08/14/2013 03:54 PM, unruh wrote:
On 2013-08-14, Mark C. Stephens ma...@non-stop.com.au wrote:
Um Let's see, Datum was bought by Austron, who was bought by ... etc.
For collectors such as myself, having this 'mature' equipment still working
is great.
Looking at Mr Malone's code, he
25 matches
Mail list logo
