On 28/06/2016 20:19, KP.Kirchdoerfer wrote:
With busybox 1.24 ntpd fails to start and the boot process continues up to a
shell login - allowing me to configure, start diagnostics and resolve errors.
With busybox 1.25 ntpd seems to loop forever if now NTP servers are found,
blocking the boot process and I never get a login to solve a possible pb or
to do a first time configuration.
Any hints how this can be solved?
There is no reason why your access to a getty/login should depend on the
launch of a NTP daemon. Your rc system apparently starts services
sequentially, with a getty after the network: this is a misdesign that
leads to the failure you're experiencing. Service managers should be able
to parallelize service startup; most don't, but at the very least distros
that use sequential service managers should start at least one early getty,
for users to still be able to log in if something fails in the boot sequence.
No matter what busybox ntpd does, it would be a good idea for you to make
sure you have a functional getty very early in the boot process.
--
Laurent
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
