Chrony instead of ntpd
Hello Team,
Does anyone has ever configured or implemented Chrony in RHEL6.x instead of ntpd? Though I was not able to find any official documentation that says Chrony can be configured and used on RHEL6.x, but I was successful in getting it installed/configured/implemented in RHEL6.x :
[root@AnsibleClient1 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.10 (Santiago) [root@AnsibleClient1 ~]# uname -a Linux AnsibleClient1 2.6.32-754.35.1.el6.x86_64 #1 SMP Wed Sep 16 06:48:01 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux [root@AnsibleClient1 ~]# pgrep chrony 2159 [root@AnsibleClient1 ~]# chronyc sources 210 Number of sources = 4 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp5.mum-in.hosts.301-mov 2 9 377 223 +5227us[+5227us] +/- 158ms ^- ntp7.mum-in.hosts.301-mov 2 9 377 403 +10ms[ +10ms] +/- 181ms ^+ gobang.hojmark.net 3 9 377 768 +2150us[+2057us] +/- 79ms ^* 165.22.211.200 3 9 377 404 -1026us[-1138us] +/- 39ms [root@AnsibleClient1 ~]# chronyc tracking Reference ID : 165.22.211.200 (165.22.211.200) Stratum : 4 Ref time (UTC) : Fri Oct 28 11:15:50 2022 System time : 1987.013183594 seconds slow of NTP time Last offset : -0.000111508 seconds RMS offset : 209.251403809 seconds Frequency : 38.976 ppm fast Residual freq : -0.007 ppm Skew : 0.710 ppm Root delay : 0.014859 seconds Root dispersion : 0.024336 seconds Update interval : 480.2 seconds Leap status : Normal
The Chrony vs ntp comparison document also talks positively for Chrony and it is a clearly a winner in most of the circumstances. https://chrony.tuxfamily.org/comparison.html
So, what I'm thinking is that is there any implications in terms of getting support from Red Hat pin case I implement Chrony in place of ntpd on RHEL6.x servers? Since Chrony is not officially called out as supported on RHEL6, I'm a bit worried. I am also aware of the fact that both can't be used same time.
Any input/insights by Red Hat team on this? Thanks!
Responses