Alan wrote:
Harlan wrote:
What you are doing is pretty much what I did when I worked on it
years ago. The trick is that what works for some folks seems to
break the driver for others, and vice-versa.
I realize that, especially with so many platorms involved. I'm just
trying to get mine
Alan,
Also please see:
http://bugs.ntp.org/show_bug.cgi?id=2177#c2
http://bugs.ntp.org/buglist.cgi?quicksearch=audio
H
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
I must admit I find NTP fascinating, depending on my mood. About 20
years
ago I had written something that attempted to measure the drift in my
computer's clock based on daily *manual* settings while listening to WWV
or
CHU. Room temperature was the biggest factor. I'm still interested in
Hi folks
Some of you may recall a question I posted several weeks ago (and to which
principally Dave Hart replied) about Leap Second and a testing scenario for our
systems.
I am processing this at the moment and found what seems to be interesting
information, unexpected to me.
I was using
Dave
Thanks for the reply.
I have now checked what has happened even more carefully and I conclude the
problem originated with the installation of the adjtimex program/RPM.
It would seem I (or someone else not sure) ran adjtimex -status to set the leap
indicator after it was installed
On Wed, May 9, 2012 at 3:12 PM, Phil Fisher phil.fis...@ipaccess.com wrote:
Once this was done, then ntptime indicates that it has been set even if the
current status shows it is not. In my opinion this is at best fallacious if
not a bug. If the Leap indicator is cleared then I would not
I'm not sure I've got the programming skills to take on much else right
now and I don't know much about Linux programming. I'd also like to get
soundmodem (by Thomas Sailer) working under OpenBSD first. I'm learning
on ntp some things that may fix soundmodem.
On the two channel idea, have
