Posted On December 17, 2020

Network Time Protocol for CentOS 8

kimconnect 0 comments
blog.KimConnect.com >> Linux >> Network Time Protocol for CentOS 8

Check hardware clock

[root@sftp testadmin]# hwclock --verbose
hwclock from util-linux 2.32.1
System Time: 1608158426.341727
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 0 seconds after 1969
Last calibration done at 0 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2018/12/16 22:40:26
Hw clock time : 2018/12/16 22:40:26 = 1608158426 seconds since 1969
Time since last adjustment is 1608158426 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2018-12-16 14:40:24.944162-08:00

Configure NTP Client:

sudo vim /etc/chrony.conf
systemctl restart chronyd

Check NTP for synchronization status:

[root@sftp testadmin]# timedatectl
Local time: Wed 2018-12-16 14:39:43 PST
Universal time: Wed 2018-12-16 22:39:43 UTC
RTC time: Wed 2018-12-16 22:39:43
Time zone: America/Los_Angeles (PST, -0800)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Post

Quick Note on Tomcat with NGINX

Below is a quick short-hand note to remind oneself to setup proxying properly between Tomcat…

Installing IBM VPN Client

On a Linux Machine # Install VPN Client shellScript=https://support.arraynetworks.net/prx/001/http/supportportal.arraynetworks.net/downloads/pkg_9_4_0_385/MP_Linux_1.2.9/MotionPro_Linux_Ubuntu_x64_build-8.sh cd Desktop wget $shellScript sudo ./MotionPro_Linux_Ubuntu_x64_build-8.sh…

How to Deploy PiHole in a Kubernetes Cluster

Step 0: Create NFS Share Ensure that the NFS share has been created with these…