Wow, I'm guessing this is the culprit ?
diff /root/ntp-4.2.6p5/ntpd/refclock_acts.c
/root/ntp-dev-4.2.7p423/ntpd/refclock_acts.c
...
144,145c149,150
< #define MODE_AUTO 0 /* automatic mode */
< #define MODE_BACKUP 1 /* backup mode */
---
#define MODE_BACKUP 0 /* backup mode */
#define MODE_AUTO 1 /* automatic mode */
...
--
Brandon Applegate - CCIE 10273
PGP Key fingerprint:
830B 4802 1DD4 F4F9 63FE B966 C0A7 189E 9EC0 3A74
"SH1-0151. This is the serial number, of our orbital gun."
On Mon, 24 Feb 2014, Harlan Stenn wrote:
Brandon Applegate writes:
In 4.2.6p5 this worked exactly as advertised...
I've been running in mode 1 (backup) for quite some time, and it's been
working fine. That is to say that a call gets made once at startup, but
by the time the other sources become reachable - no subsequent calls are
made. Calls should only been made if all other sources are unreachable.
In ntp-dev-4.2.7p423 - with the same config, calls are made pretty
frequently. The reach column 'decays' and I hear the modem fire up. I
cannot find any documentation to show me that something changed and my
config is out of date to run in -dev. Here is the relevant config:
I thought Dave Mills still has one of these setups for testing, but it
may be shut off. He's trying to avoid code maintenance these days.
I can also see if somebody else can take this over.
Are you able to compare the ACTS driver between 4.2.6 and ntp-dev?
...
I'd like to keep the -dev code running, as I'm troubleshooting a
completely unrelated bug. For now I have mode set to 2 (manual). I don't
want the phone company reliving their glory days of 30 years ago with all
these long distance calls...
The good news is that these should be *much* less expensive now, and
will even be free for a number of calling plans. But yes, if there's a
problem we should identify and fix it.
H
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
