Re: [Linuxptp-users] hardcoded expiration_date_ntp in Linuxptp

[Miroslav L. <mli...@re...>]

On Fri, Feb 11, 2022 at 03:54:12AM +0000, Nikhil Gupta wrote:
> Hi,
> 
> Can someone help me in understanding the concept behind keeping the check for expiration_date_ntp  as hardcoded value which keeps incrementing after every ~6 months.

That is the expiration of the leap table hardcoded in ts2phc. Leap
seconds are announced only about 6 months ahead.
> 
> Commits:
> commit 415b4628ecd2bf8b7de95c564e43bb0092047543 ( lstab: Bring expiration up to date. )
> commit 27bc9d52fa12b78abe0b3b73e162693938fbf498 ( lstab: update expiration to 28 December 2021 )
> 
> please suggest: can expiration_date_ntp be read from config as to avoid frequent runtime check .

The leap table can be read from the file specified by the leapfile
option. That includes the expiration date. See the ts2phc man page.

-- 
Miroslav Lichvar