On Sat, Nov 30, 2013 at 2:24 PM, ~Stack~ <[email protected]> wrote: > On 11/30/2013 01:03 PM, Nico Kadel-Garcia wrote:
>> If the upstream detection is the issue, put a "sleep 10" in the >> "start" stanza of /etc/nit.d/network. Amusingly enough, you can even >> put it in /etc/sysconfig/network-scripts/ifcfg-eth0, although that can >> get irritating and tools like system-config-network or NetworkManager >> will happily overwrite it. > > Not a bad idea. I just tried it and didn't get it to work. Maybe 10 > seconds is too short? Maybe! I haven't seen this since I started using mostly VM's for my Linux work. There's a lot of interesting complexity in the network init scripting, which makes a lot of assumptions about the state of things at various times. You might consider booting in single user mode, and single stepping your way thorugh the /etc/rc.d/rc3.d init scripts to see if and when the network is made available. If it works as expected, then yeah, a time delay on the network init script might be helpful. > I will probably just script something when I have time and shove it into > puppet. However, it seems to me that others are also having/seen this > problem. Maybe this should be something fixed upstream? > > Thanks for the help everyone! > ~Stack~ >
