On Wed, Aug 30, 2017 at 12:14:05PM -0700, Bill Unruh wrote:
> > You could run a separate server instance of chronyd on a different
> > port with HW timestamping for the monitoring client. It needs to
> > support the interleaved mode to be able to get the server's HW
> > transmit timestamps.
> The problem is interrupt contention, and clock reading contention. I once
> tried to have two different readers (chrony and ntpd, or two versions of
> chrony) reading the interrupt at the same time and one of them was about 8us
> out because it did not get the interrupt until the first one had finished.
> Ie, in monitoring you do not want to do it "on the second" since it might
> interfere with the other one.
Was that with timestamping of PPS in userspace using ioctl(TIOCMIWAIT)?
I don't think that applies to timestamping of NTP packets. A receive
timestamp is made by the kernel, not by the application, and separate
instances of chronyd are not receiving both the same packet. They
won't share the same UDP port.
When running multiple instances of chronyd, it's important than only
one of them is adjusting the clock. Also, they should be configured to
use different "port", "cmdport", "bindcmdaddress", and "pidfile".
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.