| Re: [chrony-users] leapsectz and phc refclock offset |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] leapsectz and phc refclock offset
- From: Chris Perl <cperl@xxxxxxxxxxxxxx>
- Date: Thu, 28 Sep 2017 11:40:37 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=pYZ0eLTRa/hRw+WyolxuexVw1WiHWwCzj98aRm2rYno=; b=pY3eZHMS6RwWUhFQXaeAZR7XPTz+10DCmYB5AGlp/JNOZYlkjRrdpd+YjAhsgb6cfx oxTOc9ddlL8aBKMFkwWFMcKaZiMFVnzVVxmo1dkdvsHDzffE7qyYmfhFP88isoeP02om Gs+UCjpJQlHCGQRJGP4mwTVvwkXsQbh5a5cBs=
On Fri, Sep 22, 2017 at 4:32 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
>
> An advantage of this approach is that chronyd will stop accumulating
> new samples when the PHC is no longer synchronized as phc2sys is
> continuously checking state of the PTP port.
This works to some extent, although not as robustly as I would have
hoped. If I use iptables to stop updates from getting to ptp4l, I see
phc2sys notice this and stop updating the SHM, which then causes
chrony to increment its root dispersion and then downstream clients
can see that and make proper decisions.
Unfortunately, if ptp4l isn't running (perhaps it crashed, or was
accidentally killed by an administrator), whether it leaves behind its
unix domain socket or not, it seems that phc2sys is happy to continue
taking samples in that case.
But, this sounds like an issue to be raised on the linuxptp lists.
I'm going to leave this setup running for a while and see if I can
reproduce the weird behavior I was seeing before.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.