On Tuesday, 29 August 2017 14:56:34 BST J. Roeleveld wrote: > On 29 August 2017 14:52:45 GMT+02:00, Stroller <strol...@stellar.eclipse.co.uk> wrote: > >Hello, > > > >Any recommendations for a simple NTP client? > > > >I was surprised to find the clock wrong when I logged into one of my > >systems today. > > > >On another system I have net-misc/ntp installed. On it I have: > > $ ls -1 /etc/runlevels/default/*ntp* > > /etc/runlevels/default/ntp-client > > /etc/runlevels/default/ntpd > > $ > > > >I *think* this is because ntp-client is designed not to make large > >adjustments, so ntpd is run at startup in case the clock is too far > >out. > > > >Ideally I'd like a program that performs both roles. > > > >Thanks in advance for any suggestions, > > > >Stroller. > > I switched over to chrony some time ago and it actually does what I would > logically expect ntpd to do. > > It's in portage.
Me too; many years ago, when ntpd was far less capable than it seems to be now. Chrony was designed to cope with long periods of not being connected to the internet, as in a laptop. It will step the clock at startup (you can adjust the size threshold) and slew it thereafter. It also keeps statistics of your hardware clock's performance and uses them to keep as fine a control as you like. It just works. Fit and forget. -- Regards, Peter.
