Some of my boot scripts make problems. If I boot my system ntp-client reports an error. If this happens wireless (my own script that associates with my ap) and net.eth2 (for my wireless card) do not output anything. But the scripts are started (after ntp-client?) as the connection is up and status also reports they are started. Reproducible: Sometimes Steps to Reproduce: 1. Boot the system Actual Results: - ntp-client reports an error - scripts are started, but no output Expected Results: - net.eth2 should be started before ntp-client, wireless before net - both should output anything Dependencies of wireless: depend() { use hotplug pcmcia before net } Dependencies of net.*: depend() { use hotplug pcmcia wireless }
do you use hotplug ?
I have hotplug install, as I need it for firmware-uploads (ipw2100), but I do not start the service. It has always worked that way. One thing I forgot to mention: I've just started using gensplash with splashutils from http://dev.gentoo.org/~spock/. The problems started about the same time.
I've added echo "Wireless" > /dev/tty1 to /etc/init.d/wireless and echo "Interface ${iface}" > /dev/tty1 to /etc/init.d/net.eth0 This is the result: <snip> * Starting pcmcia... cardmgr[6591]: watching 2 sockets [ ok ] * Setting wireless settings... Wireless Interface eth2 * Trying "EWORM" with encryption for device eth2... [ ok ] * Bringing eth0 up... Interface eth0 * eth0 dhcp * Bringing eth0 up in background... [ ok ] * Setting clock via the NTP client 'ntpdate'... Error : Temporary failure in name resolution 20 Aug 16:18:06 ntpdate[6830]: can't find host pool.ntp.org 20 Aug 16:18:06 ntpdate[6830]: no servers can be used, exiting * Failed to set clock [ !! ] </snip> As you can see net.eth2 is started in the background. RC_PARALLEL_STARTUP in /etc/conf.d/rc is set to "no". So why does this happen?
It happens because the hotplug scripts start the interface up for you automatically. I don't see the bug here at all, closing.
I don't see it any more. Thanks.
