Hi, I'm running an embedded system with buildroot 2010.11 and busybox 1.17.4.
I am calling udhcpc with the following command: busybox udhcpc -R -b -i eth0 and this is producing the following message: Sending discover... udhcpc: sendto: Network is down Read error: Network is down, reopening socket Sending discover... udhcpc: sendto: Network is down Read error: Network is down, reopening socket No lease, forking to background It then forks to background, but every 30 seconds or so it creates a zombie process, just named "[busybox]" in ps. When udhcpc is normally able to obtain an IP address, then I have never seen this happen. Similarly in the situation where the cable is disconnected, it also never happens. But, I think the problem *may* stem from the fact that the DHCP server on the network here sometimes cannot allocate an IP address to a client (i.e. all IP addresses are taken), and in this scenario the above behaviour occurs. Is this something that is possible to fix inside busybox? If further information/testing is required, I can certainly help out the best I can! Thanks Andy _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
