1 |
On Tuesday, 10 December 2019 06:16:50 GMT Walter Dnes wrote: |
2 |
> On Sun, Dec 08, 2019 at 01:38:59AM -0500, Walter Dnes wrote |
3 |
> |
4 |
> > question... is "rdate" a drop-in substitute for "openrdate"? |
5 |
> |
6 |
> Answering my own question... big fat NO. |
7 |
> |
8 |
> [i660][root][~] openrdate -s -n ca.pool.ntp.org (works fine) |
9 |
> |
10 |
> [i660][root][~] openrdate -s ca.pool.ntp.org (hangs and sits there) |
11 |
> |
12 |
> [i660][root][~] rdate -s ca.pool.ntp.org |
13 |
> rdate: couldn't connect to host ca.pool.ntp.org: Connection refused |
14 |
> |
15 |
> Apparently "openrdate -n" selects RFC2030 protocol. Otherwise, it |
16 |
> defaults to RFC868. That appears to be rdate's only protocol. So are |
17 |
> there any public RFC868 servers? Or are there any RFC2030 client |
18 |
> programs other than openrdate? What do people here use? |
19 |
|
20 |
I no longer use rdate and SNTP. I use chronyd which has no problem |
21 |
synchronising with various NTP servers and is suitable for systems which are |
22 |
online intermittently, like laptops. |
23 |
|
24 |
-- |
25 |
Regards, |
26 |
|
27 |
Mick |