Le 17/08/2018 à 12:38, FUSTE Emmanuel a écrit :
> Le 16/08/2018 à 11:43, FUSTE Emmanuel a écrit :
>> Le 16/08/2018 à 11:40, Miroslav Lichvar a écrit :
>>> On Thu, Aug 16, 2018 at 09:23:06AM +0000, FUSTE Emmanuel wrote:
>>>> No, with chrony the shm refclock seems to be ignored (need to retest
>>>> precisely) . The observed stratum of my chrony servers were not
>>>> refclock+1 (0+1) but the defined orphan stratum (3).
>>> Oh, you mean the servers were not synchronized to their SHM refclocks
>>> even when they were working correctly? And removing the orphan option
>>> from chrony.conf fixed that?
>> Exactly
>>> That sounds like a bug. If you have a reproducer or have more details,
>>> please let us know.
>>>
>> Ok, will find time to redo some tests and report here.
>> Thank you.
> Hello,
>
> Tested rapidly with chrony git master of June 22. Work as expected ! If
> it was a bug, it is gone.
> Will do some more tests with shm refclock and with lost of ptp link as
> the actual test is with a PHC type refclock.
> (A status positioned by writer/ptp4l , readable by the PHC device
> consumers, and reset on writer close would be great to alleviate the
> use of shm/phc2sys)
>
> Emmanuel
And I confirm. It was an old and now gone bug.
All is working as expected.
Thank you.
Emmanuel.N�����r��y隊W!���u��z����!����_jh�ʊ��+a�{.n�+�����^���y�E��^���j)\��'�ׯ��z�\��'�۱}���*+�����)��.n7��:蹹^f��X��f���܆�'�۱}���*+
