Module submission - lunar-init
duncan.gibson@xs4all.nl
duncan.gibson at xs4all.nl
Sun Apr 22 14:50:45 CEST 2007
module name : lunar-init
suggested section : utils
update (y/n) : n
bugfix (y/n) : y
security (y/n) : n
A very minor change, changing sleep 1 to sleep 2 after DHCP call.
Even with the simplest manual configuration, I found that on 50%
of reboots, the madwifi network interface wasn't ready and I would
see the following boot messages:
Hostname set to "localhost"
Domain not set
Starting messagebus [OK]
Starting Network Interface Plugging Daemon: eth0
Starting lard [OK]
Starting network:
* starting lo: [OK]
* starting ath0: DHCP failed [OK]
* starting eth0: DHCP failed [OK]
* setting default route: SIOCADDRT: Network is unreachable
failed to set gateway [Failed]
After tracing the boot sequence through, I think that there is a
timing problem where dhcpcd returns success before the child daemon
has actually managed to configure the ath0 interface.
After changing from sleep 1 to sleep 2, I've just been able to boot
10 times in a row and get a correctly configured ath0 interface.
Maybe there's a better way involving "dhcpcd -t" or something
but this appears to work for me at the moment. YMMV
Duncan / engelsman
-------------- next part --------------
--- lunar-init/network 2007-04-07 02:31:02.000000000 +0200
+++ lunar-init/network 2007-04-22 14:45:02.000000000 +0200
@@ -67,7 +67,7 @@
# This is where the magic happens
$RUNFILE $DHCP_OPTIONS $1 > /dev/null 2>&1
DHCP_EXIT=$?
- sleep 1
+ sleep 2
if [ ! -e $PIDFILE ]; then
if [ $DHCP_EXIT -eq 0 ]; then
-------------- next part --------------
lvu submit lunar-init 2a2ed0e1479c8b8e1be8c449720aadf0 -
2.6.20.7 2.6.12 gcc-4.1.2 glibc-2.3.6
More information about the Lunar
mailing list