*Output of pmc -u -b 0 'GET TIME_PROPERTIES_DATA_SET'* [root@localhost ~]# pmc -u -b 0 "GET TIME_PROPERTIES_DATA_SET" sending: GET TIME_PROPERTIES_DATA_SET 24b6fd.fffe.fc7d14-0 seq 0 RESPONSE MANAGEMENT TIME_PROPERTIES_DATA_SET currentUtcOffset 37 leap61 0 leap59 0 currentUtcOffsetValid 1 ptpTimescale 1 timeTraceable 1 frequencyTraceable 0 timeSource 0xa0
*phc2sys Command on Slave* phc2sys -s em1 -c CLOCK_REALTIME -w -m > For setting the UTC-TAI offset there is also ntptime from ntp and a > (slightly?) different adjtimex(8) which is packaged in some > distributions: We have tried setting tai_offset using ntptime and it works. We are looking at linuxptp github repo code and we don't see it setting the kernel parameter for tai_offset. Do we manually need to set it using ntptime? On Sat, Nov 3, 2018 at 6:11 AM Richard Cochran <richardcoch...@gmail.com> wrote: > On Fri, Nov 02, 2018 at 04:09:34PM +0100, Miroslav Lichvar wrote: > > On Fri, Nov 02, 2018 at 04:05:12PM +0100, Miroslav Lichvar wrote: > > > For setting the UTC-TAI offset there is also ntptime from ntp and a > > > (slightly?) different adjtimex(8) which is packaged in some > > > distributions: > > > > > > http://ftp.debian.org/debian/pool/main/a/adjtimex/ > > > > Which actually doesn't seem to support setting the offset... > > And ntptime is also read only, right? > > Thanks, > Richard >
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
