http://bugzilla.opensuse.org/show_bug.cgi?id=972471 http://bugzilla.opensuse.org/show_bug.cgi?id=972471#c50 --- Comment #50 from George Anchev --- (In reply to Marius Tomaschewski from comment #49)

(In reply to George Anchev from comment #48)

...

The question is why so far, with the exact same config, there has never been such a problem and suddenly after an update - there is one?

Perhaps you just didn't noticed it before? Or there were no obsolete ifcfg-files before? The cable of the additional link was connected?

You can be 100% sure that I would notice it. I have specifically tuned my boot up time to be very fast because I use dual boot. So when it suddenly showed 33 extra seconds I surely saw that too. It is in no way related to cables or anything else. As I mentioned - same settings, same hardware, same network, same cables. The only different thing is this extra 33 seconds.

...

Also - if I lower manually WAIT_FOR_INTERACES to (say) 3 seconds - what could be the negative impact?

ifup will return after 3 sec, setup will happen in background and when you have services which bind to specific IPs, the'll fail.

Thanks for explaining. That is surely not desired. -- You are receiving this mail because: You are on the CC list for the bug.