On 10/5/2022 11:38 PM, Miroslav Lichvar wrote:
> Before setting the new frequency offset on a clock update, compare the
> current frequency with the value saved from the previous update and
> print a warning message if they are different.
>
> This should detect misconfigurations where multiple
Before setting the new frequency offset on a clock update, compare the
current frequency with the value saved from the previous update and
print a warning message if they are different.
This should detect misconfigurations where multiple processes are trying
to control the clock (e.g. another ptp4
