Hi,
diff -u chrony-1.24/debian/init.d chrony-1.24/debian/init.d
--- chrony-1.24/debian/init.d
+++ chrony-1.24/debian/init.d
@@ -9,8 +9,8 @@
# Provides: chrony
# Required-Start: $remote_fs
# Required-Stop: $remote_fs
-# Should-Start: $syslog $network $named
-# Should-Stop: $syslog $network $named
+# Should-Start: $syslog $network $named $hwclock
+# Should-Stop: $syslog $network $named $hwclock
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Controls chronyd NTP time daemon
@@ -29,7 +29,7 @@
{ # Do we have a default route? If so put chronyd online.
if timelimit -q -s9 -t5 -- netstat -rn 2>/dev/null | grep UG | cut -f 1 -d ' ' | grep -q '0\.0\.0\.0'
then
- sleep 1 # Chronyd can take a while to start.
+ sleep 2 # Chronyd can take a while to start.
KEY=$(awk '$1 ~ /^commandkey$/ { print $2; exit}' /etc/chrony/chrony.conf)
PASSWORD=`awk '$1 ~ /^'$KEY'$/ {print $2; exit}' /etc/chrony/chrony.keys`
# Make sure chronyc can't hang us up.
isn't there anything better than doubling the sleep timeout to determine if
chrony is indeed awake?
Kind regards,
Philipp Kern
Attachment:
signature.asc
Description: Digital signature