On Mon, Mar 13, 2023 at 10:29:55AM +0700, James Clark wrote:
> Would it make sense to set currentUtcOffsetValid to 1 if the TAI
> offset is set in the kernel to a non-zero value (which would typically
> come from running an NTP server)?
The time in the PHC is not necessarily connected to the Linu
On Mon, Mar 13, 2023 at 9:07 AM Richard Cochran
wrote:
>
> The UTC
> offset can only be valid if the computer has access to the global time
> distribution system (ie GPS or NTP) and monitors leap second
> announcements in real time.
>
> A hard coded configuration setting would be morally wrong!
On Mon, Mar 13, 2023 at 01:31:56AM +0100, Georg Sauthoff wrote:
> However, I'm curious, is this a deliberate design decision to not provide
> a configuration setting for the currentUtcOffsetValid value, as well?
> Or is such configuration simply missing because nobody has bothered adding
> one?
Hello,
by default, ptp4l sends its PTP announce messages with currentUtcOffset
set to 37 and currentUtcOffsetValid set to 0.
AFAICS, there is no configuration file pragma for setting
currentUtcOffsetValid to 1 to make sure that ptp4l is always sending
all announce messages with that value.
I kno
