[Bug 288361] check_link_down delay of 10 to low

[Red Hat Bugzilla]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

https://bugzilla.redhat.com/show_bug.cgi?id=288361

Nadav Har'El  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #9 from Nadav Har'El  2010-04-01 11:04:08 EDT ---
I would like to urge you to reopen this bug, and fix it. Despite it being
closed NOTABUG, it *is* a bug.

For the vast majority of today's users, a network *is* available, and giving up
after 5 seconds is non-sensical. Worse, the message you show is:

"Determining IP information for eth0... failed; no link present.  Check cable?"

Which gives two confusing, false leads - the first part leads the user to
assume the problem is somehow related to DHCP, while the second part leads the
user to check the cable. The user can wiggle the cable and "service network
restart" till hell freezes over, and it won't help until he increases
LINKDELAY.

Since this is a relatively common problem (see also bug 425877 and bug 470327.
It also happens frequently in my company's network), shouldn't be the *minimal*
fix to this bug to add a short reference to LINKDELAY in the above message?

Frankly, I'm not sure why you are worried about increasing the default
LINKDELAY from 5 to something higher, say 10 or 20. Users that don't have no
network setup at all will not experience this delay. Users with a functional
network will not experience this delay (the loop stops as soon as the link
comes up). The only people who will experience the longer delay are people who
have set up the network (so they want it up) but their network link is indeed
down. The extra delay of 20 seconds is probably the least of their worries in
this case. And don't forget to balance this with all the people for whom Fedora
will just give up after 5 seconds and never connect to the Internet - while
Windows, Ubuntu, and others will not give up so quickly and eventually (say,
after 6 seconds ;-)) connect.