Thanks, Richard. We are able to modify currentUtcOffsetValid and timeTraceable parameters now on the master node.
@Miroslav, after setting currentUtcOffsetValid and timeTraceable parameters to 1, we still get clock_gettime(CLOCK_TAI) same as clock_gettime(CLOCK_REALTIME). And we still don't see kernel parameter tai_offset being set (verified by ntptime command) Are we missing something? On Wed, Oct 31, 2018 at 8:04 PM Richard Cochran <richardcoch...@gmail.com> wrote: > On Wed, Oct 31, 2018 at 07:36:25PM +0530, Dolly Gyanchandani wrote: > > We donot have a GrandMaster yet. Is there a way we can configure > > currentUtcOffsetValid and timeTraceable to be 1 ? > > For that we have the GRANDMASTER_SETTINGS_NP management message. > > - values used when nodes becomes the GM > - SET action useful for GPS time server > > clockClass 248 > clockAccuracy 0xfe > offsetScaledLogVariance 0xffff > currentUtcOffset 35 > leap61 0 > leap59 0 > currentUtcOffsetValid 0 > ptpTimescale 0 > timeTraceable 0 > frequencyTraceable 0 > timeSource 0xa0 > > HTH, > Richard >
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
