Re: [PATCH] ntpd: make NTP client Y2036-ready

2022-05-09 Thread Miroslav Lichvar
On Tue, May 10, 2022 at 12:50:11AM +0800, Kang-Che Sung wrote: > On Monday, May 9, 2022, Miroslav Lichvar wrote: > > The 32-bit integer part of the NTP timestamp overflows in year 2036, > > which starts the second NTP era. > > > > Modify the timestamp conversion to shift values between 1900-1970

Re: [PATCH] ntpd: make NTP client Y2036-ready

2022-05-09 Thread Kang-Che Sung
On Monday, May 9, 2022, Miroslav Lichvar wrote: > The 32-bit integer part of the NTP timestamp overflows in year 2036, > which starts the second NTP era. > > Modify the timestamp conversion to shift values between 1900-1970 (in > the first era) to the second era to enable the client to

[PATCH] ntpd: make NTP client Y2036-ready

2022-05-09 Thread Miroslav Lichvar
The 32-bit integer part of the NTP timestamp overflows in year 2036, which starts the second NTP era. Modify the timestamp conversion to shift values between 1900-1970 (in the first era) to the second era to enable the client to synchronize correctly until year 2106 (assuming 64-bit time_t).