Re: NTP change (was Re: Schedule for Wednesday's FESCo Meeting (2021-01-06))

2021-01-07 Thread Miroslav Lichvar
On Wed, Jan 06, 2021 at 07:40:07AM -0600, Chris Adams wrote: > Once upon a time, Miroslav Lichvar said: > > If the bumps were due to insufficient documentation (e.g. the > > ntp-refclock man page), would you have any suggestions on how to > > improve it, or submit a patch? > > Since I'm using a r

Re: NTP change (was Re: Schedule for Wednesday's FESCo Meeting (2021-01-06))

2021-01-06 Thread Chris Adams
Once upon a time, Miroslav Lichvar said: > On Tue, Jan 05, 2021 at 08:30:39AM -0600, Chris Adams wrote: > > Once upon a time, Zbigniew Jędrzejewski-Szmek said: > > > #2517 F34 Change: ntp replacement > > > https://pagure.io/fesco/issue/2517 > > > APPROVED (+5, 0, 0) > > > > I changed my stratum 1

Re: NTP change (was Re: Schedule for Wednesday's FESCo Meeting (2021-01-06))

2021-01-06 Thread Miroslav Lichvar
On Tue, Jan 05, 2021 at 08:30:39AM -0600, Chris Adams wrote: > Once upon a time, Zbigniew Jędrzejewski-Szmek said: > > #2517 F34 Change: ntp replacement > > https://pagure.io/fesco/issue/2517 > > APPROVED (+5, 0, 0) > > I changed my stratum 1 server from ntpd to chronyd+ntp-refclock... had a > few

NTP change (was Re: Schedule for Wednesday's FESCo Meeting (2021-01-06))

2021-01-05 Thread Chris Adams
Once upon a time, Zbigniew Jędrzejewski-Szmek said: > #2517 F34 Change: ntp replacement > https://pagure.io/fesco/issue/2517 > APPROVED (+5, 0, 0) I changed my stratum 1 server from ntpd to chronyd+ntp-refclock... had a few small bumps to figure out (getting the NTP, PPS, and chrony services corr