On 28/10/2010 20:39, Andrew O. Shadoura wrote:
Hello.
On Monday 13 September 2010 11:52:51 Eric Valette wrote:
As subject says, its a weird problem, as neither the config file is
broken but changing timing slightly make it work. It fails alaos with lo
so it is not a driver problem. I guess the way to determine the
interface has chnaged slightly due to libc chnage.
BTW there are a couple of use before set during the compilation, just in
the area of the target_inteface variables.
Eric, have you found a work-around for your issue? Or, any details?
Well, I dunno: I found that failing to receive an ip address for a NAS
without any no IP interface is too dangerous (I had to ask a friend to
solder a serial console using the relevant information I found on
internet!).
Now I have a fixed IP address and do not use dhclient anymore on this
machine. The strace suggest a timing problem between the hardware link
up and the other set of command. I also saw report about lo failing on
ubuntu when the ifupdown command failed.
--eric
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
