On Thu, May 11, 2023 at 01:01:54PM -0300, Elder Costa wrote:
> The master offset increases, non monotonically but with a very definite
> trend, whether with or without the step_threshold parameter.
> What am I missing?
Maybe you have ntpd or systemd timesync or chrony running on the
client and/o
I had already notice this while trying to solve the clock sync issue of
the other thread.
Test setup is two Fitlet PCs, connected point-to-point.
The master offset increases, non monotonically but with a very definite
trend, whether with or without the step_threshold parameter.
$ uname -srvm
Hello, Miroslav, thank you very much. It worked.
I stopped using the "--" because some options generated an error.
For example:
cve@cve-sbc-flt2:~/work/linuxptp-3.1.1$ sudo ptp4l -4 -S -m -q
--clientOnly=1 --step_threshold=0.001 -i enp3s0
ptp4l: unrecognized option '--clientOnly=1'
As ptp4l did
On Thu, May 11, 2023 at 08:45:02AM -0300, Elder Costa wrote:
> Hello, Richard, thank you for the explanation. It confirms my initial
> understanding of the
> parameter. But I must be doing something wrong as I am not getting
> this clock step.
> cve@cve-sbc-flt2:~$ sudo ptp4l -4 -S -s -m -q step_t
Em qua., 10 de mai. de 2023 às 19:25, Richard Cochran
escreveu:
>
> But if you set --step_threshold=X, the program will use method #1
> whenever the estimated offset exceeds X.
Hello, Richard, thank you for the explanation. It confirms my initial
understanding of the
parameter. But I must be doi
