[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #JEC-686496]: no ntpdate in RedHat/CentOS8 questions

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #JEC-686496]: no ntpdate in RedHat/CentOS8 questions
  • Date: Fri, 22 May 2020 12:27:25 -0600
Hi Jonathan,

> Yes, on our systems we have configuration mgmt in place to ensure chronyd
> is installed and configured (to run as a daemon/service).

Good.

> Because our
> systems are VMs that are either provisioned of cloned, I don't know how it
> comes "out of the box" from RH/Centos (ie, I have not built a RH8 system
> from scratch),

Ok.

> We also monitor for time skew on our systems.
> 
> FWIW... chronyd can be run like ntpdate to query the system clock status, a
> la:
> 
> chronyd -Q 'pool pool.ntp.org iburst'

Good to know. Thanks!

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: JEC-686496
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.