| [chrony-users] chronyd.service slow start on boot? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] chronyd.service slow start on boot?
- From: a58bf2b4-3c17-40c6-8709-d1b882bdbfb3@xxxxxxxxx
- Date: Sat, 09 Oct 2021 18:30:24 -0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=slmail.me; i=@slmail.me; q=dns/txt; s=dkim; t=1633804224; h=message-id : date : subject : from : to; bh=oeqEZd+k9cEf9Kny337wSOrINHNHhs1Y5nb9jQmOwks=; b=LQr0kYM90cXGbkptHHpAhTWrRhsLJJhEpYZPzYVsp+C98y0S+C1yaJIKNq4yyNf+GgRQ+ SKQZpiQtqJ8gRE83M9+WvfhxloytVObVP03Yz8DZaR0mCMe3qh9tfnYHEj30ffXICkmb6W5 V6t4hB1Scnt3Tt/BO7JsiSrLQVQsIig=
Hi,
I've recently switched to chrony on my Arch Linux laptop and systemd consistently reports 8 to 9 seconds for this service to start. I don't think it's actually slowing the overall boot process because services can start on parallel, but anyway I'm asking if this much time is rather expected. All my sources are marked as offline in the config.
I'm copying here the service unit file and relevant info from my system running chrony 4.1:
#####
[Unit]
Description=NTP client/server
Documentation=man:chronyd(8) man:chrony.conf(5)
After=ntpdate.service sntp.service ntpd.service
Conflicts=ntpd.service systemd-timesyncd.service
ConditionCapability=CAP_SYS_TIME
[Service]
Type=forking
PIDFile=/run/chrony/chronyd.pid
EnvironmentFile=-/etc/sysconfig/chronyd
ExecStart=/usr/bin/chronyd $OPTIONS
PrivateTmp=yes
ProtectHome=yes
ProtectSystem=full
[Install]
WantedBy=multi-user.target
#####
cat /etc/sysconfig/chronyd
OPTIONS='-r -s'
graphical.target @9.031s
└─multi-user.target @9.031s
└─chronyd.service @418ms +8.612s
└─basic.target @415ms
└─sockets.target @414ms
└─dbus.socket @413ms
└─sysinit.target @405ms
└─systemd-backlight@backlight:amdgpu_bl0.service @2.520s +6ms
└─system-systemd\x2dbacklight.slice @678ms
└─system.slice
└─-.slice
19:28:29 systemd[1]: Starting NTP client/server...
19:28:29 chronyd[688]: chronyd version 4.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
19:28:26 chronyd[688]: System time set from RTC
19:28:26 chronyd[688]: Frequency -0.115 +/- 0.020 ppm read from /var/lib/chrony/drift
19:28:26 chronyd[688]: Using right/UTC timezone to obtain leap second data
19:28:34 chronyd[688]: System clock off from RTC by 0.080163 seconds (slew)
19:28:34 systemd[1]: Started NTP client/server.
19:28:42 chronyd[688]: Loaded dump file for xx.xx.xx.xx
19:28:42 chronyd[688]: Loaded dump file for xx.xx.xx.xx
19:28:42 chronyd[688]: Loaded dump file for xx.xx.xx.xx
19:28:42 chronyd[688]: Loaded dump file for xx.xx.xx.xx
19:28:42 chronyd[688]: Loaded dump file for xx.xx.xx.xx
19:28:42 chronyd[688]: Selected source xx.xx.xx.xx
19:28:42 chronyd[688]: System clock TAI offset set to 37 seconds
According to journalctl output server startup time is around 5-6 seconds...
Thanks.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.