/etc/init.d/ntp-client should "need" net rather than just "after." If all interfaces fail to start, the system will hang on ntp-client. I use ntpd -q for ntp-client. Reproducible: Always Steps to Reproduce: 1. rc-update add ntp-client default 2. disable or break your network interface init 3. reboot Actual Results: system hang on ntp-client init Expected Results: skip ntp-client since net is down.
*** This bug has been marked as a duplicate of bug 439564 ***
This is not a duplicate. The cited bug broke the functionality that was there before and violated the principle of least surprise. bug 439564 broke what was working for probably 99% of Gentoo users and requires them to make a modification to /etc/conf.d/ntp-client rather than the 1% doing something different having to modify /etc/conf.d/ntp-client - and this was done with not even a note in /etc/conf.d/ntp-client. Change it back or at the very least, add a comment to /etc/conf.d/ntp-client.
Having your interfaces break your boot is the principle of least surprise; if you want your system to boot regardless, make your system not depend on ntp-client. For details wrt the "need net" removals, see the following gentoo-dev ML post: http://www.gossamer-threads.com/lists/gentoo/dev/261562
I think that ntp-client is a special case because 1. it is not actually a running daemon that will need to be restarted or stopped 2. it does not fork and remains in the foreground for its init. (does not use start-stop-daemon) With the present situation, my interfaces breaking my boot means it hangs until I go to the actual console, give it the three finger salute and boot into single user mode. Telling me to not use stable, useful software is not an answer.
(In reply to Mark Keisler from comment #4) > I think that ntp-client is a special case because > 1. it is not actually a running daemon that will need to be restarted or > stopped > 2. it does not fork and remains in the foreground for its init. (does not > use start-stop-daemon) So, this case would hang when there is no net; which is why there is "after net" to ensure that it runs after the network has been set up, removing "after net" would still hang the boot given this case. This is no different from what it would do if there were "need net" instead of "after net"; which has nearly no difference, as it only has some differences in term of restarting which does not pertain to a hanging boot. > With the present situation, my interfaces breaking my boot means it hangs > until I go to the actual console, give it the three finger salute and boot > into single user mode. Telling me to not use stable, useful software is not > an answer. For answers to support questions, like booting a system without net; you can find help on the Gentoo forums, mailing lists or #gentoo on the freenode IRC network.
I beg to differ. My only net interface besides loopback failed and ntp-client tried to start and hung with the default "after net".
(In reply to Mark Keisler from comment #6) > I beg to differ. My only net interface besides loopback failed and > ntp-client tried to start and hung with the default "after net". I assume there to be a bug elsewhere in the chain if that is the case.
