the ntp initskript will only run at first connection try. If this fails
and the connection can established later DNS will not work if the clock
is too far away.
Signed-off-by: Arne Fitzenreiter <arne_f@ipfire.org>
etc/system-release
etc/issue
+etc/rc.d/init.d/ntp
+etc/rc.d/init.d/unbound
var/ipfire/langs
fi
if [ -e /var/ipfire/red/active ]; then
boot_mesg ""
-
- host ping.ipfire.org > /dev/null 2>&1
- if [ "${?}" != "0" ]; then
- boot_mesg "DNS not work ... init with ntp.ipfire.org at 81.3.27.46 ..."
- loadproc /usr/local/bin/settime 81.3.27.46
- boot_mesg "Setting time on boot..."
- fi
-
loadproc /usr/local/bin/settime $(cat /var/ipfire/time/settime.conf)
else
boot_mesg " ERROR! Not online!"
# Update hosts
update_hosts
+
+ # If DNS still not work try to init ntp with
+ # hardcoded ntp.ipfire.org (81.3.27.46)
+ if [ -e /var/ipfire/red/active ]; then
+ host 0.ipfire.pool.ntp.org > /dev/null 2>&1
+ if [ "${?}" != "0" ]; then
+ boot_mesg "DNS still not work ... init time with ntp.ipfire.org at 81.3.27.46 ..."
+ loadproc /usr/local/bin/settime 81.3.27.46
+ fi
+ fi
;;
stop)