HAUTZ Gilles wrote:
Hi all,
I've discovered a "bug" in the ntp boot script.
If there is no network connectivity or a DNS problem. The computer won't
boot and stay at NTP starting.
I think we should first check that we can reach the ntp server before
trying to start ntpd.
I know that RH try first to ntpdate the server then if it works start
the ntp daemon.
Yes, that's true. I've always worked round it by making sure the ntp script is
the last to run so if it hangs it doesn't matter. I suppose the solution would
be to try and ping the time server, but even that might hang? Maybe it would
just be simpler to set a time limit of 30 seconds or something and if it hasn't
connected to the time server the script should fail with a warning?
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
