I think the timeout is the best solution, but how to implement that with
the bootscript ?
Andrew Benton a écrit :
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?
begin:vcard
fn:Gilles HAUTZ
n:HAUTZ;Gilles
org:MANA S.A.S.;Production
email;internet:[EMAIL PROTECTED]
title;quoted-printable:Sp=C3=A9cialiste syst=C3=A8mes
tel;work:479956
x-mozilla-html:TRUE
url:http://www.mana.pf
version:2.1
end:vcard
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
