Hi All, If the output of this:
># phc_ctl ens2f1 get cmp phc_ctl[2350429.937]: clock time is 1589981848.451319038 or Wed May 20 15:37:28 2020 phc_ctl[2350429.937]: offset from CLOCK_REALTIME is -37001639797ns now means that the NTP-synced clock of the PC where all this is running (CLOCK_REALTIME) is -37001639797ns offset of the PHC on NIC ens2f1 than this is exactly what I needed. I hope this is true. And I really would like to contribute, but I think I've to learn a lot more programming for that. But maybe thats a good start. Thanks a lot all for your help. If someone could please confirm this one last question. kind regards Werner On Wed, May 20, 2020 at 3:04 PM Richard Cochran <richardcoch...@gmail.com> wrote: > On Wed, May 20, 2020 at 10:01:48PM +1000, David Mirabito wrote: > > The phc_ctl utility has a 'cmp' command which can "compare PHC offset to > > CLOCK_REALTIME" . Is that the building block you're looking for? > > Oh wow, I totally forgot about that! > > Yeah, that is just what Werner would need, if I'm not wrong. > > Thanks, > Richard >
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
