앞으로도 초니는 계속 전진하겠습니다.

나는 centos 8 시스템에 chrony를 설치했고 2일마다 약 2시간씩 미래 시간을 설정합니다. 계속해서 서비스를 다시 시작하고 ntpdata수정해야 하는데 그게 짜증스럽네요. 구성을 조작해 보았지만 어떻게 해야 할지 잘 모르겠습니다. 어떤 아이디어가 있나요?

내 구성은 다음과 같습니다.

# Please consider joining the pool (http://www.pool.ntp.org/join.html).
pool 2.centos.pool.ntp.org iburst

# Record the rate at which the system clock gains/losses time.
driftfile /var/lib/chrony/drift

# Allow the system clock to be stepped in the first three updates
# if its offset is larger than 1 second.
makestep 1000 10

# Enable kernel synchronization of the real-time clock (RTC).
rtcsync

# Enable hardware timestamping on all interfaces that support it.
#hwtimestamp *

# Increase the minimum number of selectable sources required to adjust
# the system clock.
#minsources 2

# Allow NTP client access from local network.
#allow 192.168.0.0/16
allow 192.168.1.0/24
# Serve time even if not synchronized to a time source.
#local stratum 10

# Specify file containing keys for NTP authentication.
keyfile /etc/chrony.keys

# Get TAI-UTC offset and leap seconds from the system tz database.
leapsectz right/UTC

# Specify directory for log files.
logdir /var/log/chrony

# Select which information is logged.
#log measurements statistics tracking

[server ~]$ chronyc tracking
Reference ID    : A29FC87B (time.cloudflare.com)
Stratum         : 4
Ref time (UTC)  : Fri Mar 25 08:22:28 2022
System time     : 3662.770263672 seconds fast of NTP time
Last offset     : +0.000199583 seconds
RMS offset      : 37.570960999 seconds
Frequency       : 14.564 ppm slow
Residual freq   : -0.000 ppm
Skew            : 0.007 ppm
Root delay      : 0.038045153 seconds
Root dispersion : 0.000602906 seconds
Update interval : 1036.4 seconds
Leap status     : Normal

[server ~]$ date
Fri Mar 25 11:31:15 EET 2022