Peter Humphrey wrote: > On Tuesday, 29 August 2017 14:56:34 BST J. Roeleveld wrote: >> On 29 August 2017 14:52:45 GMT+02:00, Stroller > <[email protected]> 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. >
Same here. For some reason, I updated NTP and it wouldn't work anymore. I tried different configs and even a fresh config, still wouldn't work. I switched to chrony and the only thing I recall changing, the server it checks in with. I found a few that were really close and the data could go really fast. I still have ntp installed tho. I use that command to see if it is working still, once in a blue moon. <<<<< ntpdate -b -u -q pool.ntp.org >>>>> server 4.53.160.75, stratum 2, offset -0.002993, delay 0.07785 server 138.236.128.112, stratum 2, offset -0.005360, delay 0.08356 server 208.76.53.137, stratum 2, offset -0.003967, delay 0.06667 server 173.203.211.73, stratum 2, offset 0.003827, delay 0.06401 29 Aug 13:18:11 ntpdate[842]: step time server 173.203.211.73 offset 0.003827 sec For me, that's close enough. ;-) Dale :-) :-)
