ntpd is doing something I don't like and I want to find a way to stop it.
I've got a box that is intermittently connected and I am using a tool to calibrate the system clock to keep it running linearly and accurately. (It's a custom tool but it's not important exactly what it is.)
The tool uses adjtimex() to set the tick/freq values to calibrate the system clock. Now, since I know this one clock is pretty accurate I want to use ntpd to serve time to the rest of the internally-networked machines. (They'll just ntpdate every once in a while to synchronize their clocks.)
The problem is that when ntpd starts is mutates my calibrated values (resetting the "freq" to 0, most of the time) and causing the machine to become really inaccurate. My /etc/ntp.conf doesn't point to any external servers for synchronization but I can't find an option to pass to ntpd to tell it to just accept the clock as-is and serve its time to external clients.
Thoughts?
Paul Braman
Linear Mode
