Hi,
The ntp test uses the ntpdate command:
Command: ntpdate -u -q -p 1 192.168.192.1 2>&1
server 192.168.192.1, stratum 3, offset 0.000055, delay 0.02580
18 Aug 12:19:03 ntpdate[75689]: adjust time server 192.168.192.1 offset 0.000055 sec
It shouldn't matter if the system is using chrony for timekeeping
because ntpdate with '-q' is a simple ntp protocol query that doesn't
attempt to change anything.
You may be able to cook something up with the chronyd command using the
option '-Q' but it looks quite messy to do.
Cheers,
Brian
▸ quoted from Mike Burger
On 17/8/18 1:47 am, Mike Burger wrote:
Good morning,
I'm installing Xymon on an Amazon Linux 2 instance (RHEL/CentOS 7
equivalent) and noticed that, although Chrony is installed on the
instance, the ntp and ntpdate packages were installed as pre-reqs for
the JC's xymon package.
I was just wondering:
* Why is ntp/ntpdate a requirement for the Xymon package?
* Does Chrony not have equivalent functionality?
Thanks.
--
Mike Burger
http://www.bubbanfriends.org
"It's always suicide-mission this, save-the-planet that. No one ever
just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1