Danny Mayer wrote:
I have never seen someone who says they are a gpsd maintainer on here
but we would be glad to have them comment on this if they are here.
Anyone know where they usually hang out?
gpsd has its own mailing list, which is where support is offered,
[EMAIL PROTECTED] . All of
Johan Swenker wrote:
Hi,
Today I found why my gps receiver stopped working last newyears eve.
Apparently gpsd has a leapyear bug (repaired on january 1st). Thus it
reported a january 21 while it still was january 20. Which was discarded
by ntp. After compiling the new version of gpsd, my
Danny Mayer [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Harlan Stenn wrote:
When somebody automatically types 0.ca.pool.ntp.org it *might*
go to my IP address, but I don't have a redirect setup for that
hostname. I am using thttpd. How can I make a redirect for
*.pool.ntp.org
After reading the documentation (took all of a minute or two), thttpd does
support multihoming, but it doesn't look like it supports wildcards.
For that you will probably have to run apache or another web server that
does support wildcards.
Or you could just have some text on your front page
Having run NTP stably now for three days on a machine I previously ran
chrony on , I compared the control of the
clock on that machine with chrony and with ntp (the comparison is obviously
sequential, since both cannot run on the same machine at the same time.)
The chrony run was from Jan 13.5 to
[EMAIL PROTECTED] (David Woolley) writes:
In article [EMAIL PROTECTED],
Bill Unruh [EMAIL PROTECTED] wrote:
Offset error:
NTP: Mean=-3.1usec, Std Dev=63.1usec
If offset is the value reported by ntpq, please note that, when ntpd
is locked up, this is an indication of the instantaneous
On Mon, 21 Jan 2008 09:40:31 -0800, Dennis Hilberg, Jr. wrote:
statistics loopstats peerstats clockstats
You won't generate any clockstats unless your using a clock driver.
Which I assume requires an external real clock, GPS, WWV, etc.?
Using 'noquery' prevents people from using ntpq and
hal-usenet wrote:
Dean Messing wrote:
I am seeing strange behaviour on my _x86_64 Fedora 7 desktop
workstation with regard to the system-cmos time that `adjtimex'
reports.
snip
It seems that leaves two other possibilities: a bug in adjtimex or a
bug in the kernel. That's where I am
[EMAIL PROTECTED] (David Woolley) writes:
In article [EMAIL PROTECTED],
Unruh [EMAIL PROTECTED] wrote:
No, the offset is the value reported in loopstats.
Same thing. If chrony is reporting the same measurements, neither set of
measurements is particularly valid. You need to measure the
Unruh wrote:
correction applied on that sample.
No, this is offset as measured by the ntp procedure ( (t1+t4-t2-t3)/2 )
No, that's wrong. It is very carefully described in the NTPv4 draft
section 8 (p27):
theta = T(B) - T(A) = 1/2 * [(T2-T1) + (T3-T4)]
Not only do you have the wrong
Unruh wrote:
All I say is that the experiments I have carried out show that ntp is slow
to converge if it starts of badly, and leaves the offset scatter larger
than chrony does. It does have a smaller scatter in the rate.
But you are using an extremely old version of ntp and things have
[EMAIL PROTECTED] (Danny Mayer) writes:
Unruh wrote:
All I say is that the experiments I have carried out show that ntp is slow
to converge if it starts of badly, and leaves the offset scatter larger
than chrony does. It does have a smaller scatter in the rate.
But you are using an
[EMAIL PROTECTED] (Danny Mayer) writes:
Unruh wrote:
correction applied on that sample.
No, this is offset as measured by the ntp procedure ( (t1+t4-t2-t3)/2 )
No, that's wrong. It is very carefully described in the NTPv4 draft
section 8 (p27):
theta = T(B) - T(A) = 1/2 * [(T2-T1) +
13 matches
Mail list logo
