1 |
Peter Humphrey wrote: |
2 |
> On Tuesday, 29 August 2017 14:56:34 BST J. Roeleveld wrote: |
3 |
>> On 29 August 2017 14:52:45 GMT+02:00, Stroller |
4 |
> <stroller@××××××××××××××××××.uk> wrote: |
5 |
>>> Hello, |
6 |
>>> |
7 |
>>> Any recommendations for a simple NTP client? |
8 |
>>> |
9 |
>>> I was surprised to find the clock wrong when I logged into one of my |
10 |
>>> systems today. |
11 |
>>> |
12 |
>>> On another system I have net-misc/ntp installed. On it I have: |
13 |
>>> $ ls -1 /etc/runlevels/default/*ntp* |
14 |
>>> /etc/runlevels/default/ntp-client |
15 |
>>> /etc/runlevels/default/ntpd |
16 |
>>> $ |
17 |
>>> |
18 |
>>> I *think* this is because ntp-client is designed not to make large |
19 |
>>> adjustments, so ntpd is run at startup in case the clock is too far |
20 |
>>> out. |
21 |
>>> |
22 |
>>> Ideally I'd like a program that performs both roles. |
23 |
>>> |
24 |
>>> Thanks in advance for any suggestions, |
25 |
>>> |
26 |
>>> Stroller. |
27 |
>> I switched over to chrony some time ago and it actually does what I would |
28 |
>> logically expect ntpd to do. |
29 |
>> |
30 |
>> It's in portage. |
31 |
> Me too; many years ago, when ntpd was far less capable than it seems to be |
32 |
> now. |
33 |
> |
34 |
> Chrony was designed to cope with long periods of not being connected to the |
35 |
> internet, as in a laptop. It will step the clock at startup (you can adjust |
36 |
> the size threshold) and slew it thereafter. It also keeps statistics of your |
37 |
> hardware clock's performance and uses them to keep as fine a control as you |
38 |
> like. |
39 |
> |
40 |
> It just works. Fit and forget. |
41 |
> |
42 |
|
43 |
Same here. For some reason, I updated NTP and it wouldn't work |
44 |
anymore. I tried different configs and even a fresh config, still |
45 |
wouldn't work. I switched to chrony and the only thing I recall |
46 |
changing, the server it checks in with. I found a few that were really |
47 |
close and the data could go really fast. I still have ntp installed |
48 |
tho. I use that command to see if it is working still, once in a blue |
49 |
moon. |
50 |
|
51 |
<<<<< ntpdate -b -u -q pool.ntp.org >>>>> |
52 |
server 4.53.160.75, stratum 2, offset -0.002993, delay 0.07785 |
53 |
server 138.236.128.112, stratum 2, offset -0.005360, delay 0.08356 |
54 |
server 208.76.53.137, stratum 2, offset -0.003967, delay 0.06667 |
55 |
server 173.203.211.73, stratum 2, offset 0.003827, delay 0.06401 |
56 |
29 Aug 13:18:11 ntpdate[842]: step time server 173.203.211.73 offset |
57 |
0.003827 sec |
58 |
|
59 |
|
60 |
For me, that's close enough. ;-) |
61 |
|
62 |
Dale |
63 |
|
64 |
:-) :-) |