Hello all,

I've set up the 6.2 BLFS NTP 4.2.0a package on my LFS server, and all went well. I then encountered problems with the BIND package; and left my /etc/resolve.conf with an invalid nameserver (the ip of my LFS computer: 192.168.0.2).

I tried a reboot and noticed that while BIND will fail on startup, but startup will continue, NTP will not be able to start (since it can't resolve the hosts in ntp.conf), and system will block at that point.

I had to reboot with the LFS LiveCD, fix my resolve.conf, and reboot.

I guess this isn't really a NTP bug, but rather a bootscript problem for NTP. NTP should fail, but boot sequence should continue.

Julien

--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to