On 07/27/2014 08:08 AM, Grand Duet wrote: > > If eth0 starts after lo, then I have the right /etc/resolv.conf > file, however if lo starts after eth0, then the DNS IPs in > resolv.conf file are overwritten with dummy instruction > for lo interface. > > But, now, after your suggestion, I have looked into > my /etc/rc.conf file, and have found there the option > rc_parallel="NO" > which softens my previous arguments a bit, but not completely: > may be lo and eth0 are brought up not in parallel but in different > order, anyway. >
The first thing I do on any new build is disable network hotplugging in /etc/rc.conf, as I've run into lots of problems, especially if you have multiple network devices and need to bring them up in a specific order. udev processes these items and apparently brings the interfaces up on its own unless you tell it otherwise (the !net.* in rc.conf). I've just gotten used to disabling that automagic because I want things to start in a certain order and udev can mess that up. During boot, you'll see something like 'processing events' and that's when udev is automagically doing it's start. From what I recall, this happens before the boot runlevel. So yes, it can mess things up as you've seen. I've never had the issue you have, even though I use a static ip, routes and dns servers in /etc/conf.d/net, but I would presume that this is just udev. FYI it doesn't always process things in the same order, as I've experienced with udev and my TV tuner cards... it can be random. Dan
