Bug 116089
Summary: | Network startup should be optional with no penalty for non-starting. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | J.B. Nicholson-Owens <jbn> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1 | CC: | harald, mitr, rvokal |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-29 01:33:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
J.B. Nicholson-Owens
2004-02-18 04:10:34 UTC
It would have to be a separate flag... currently ONBOOT is either 'yes' or 'no'; no 'maybe'. I support the intention of this RFE, but like to propose an alternative method of achieving it. In fact, I like to propose to do the same as what SuSE does *in the case* where the BOOTPROTO is DHCP. If the DHCP client doesn't get an IP address within a fixed time frame (eg, 5sec) put it into the background and continue with the boot process. This is especially useful for wireless cards in laptops, especially if the DHCP client keeps trying in the background and brings the interface up as soon as the machine moves within the range of a suitable wireless network. Our solution for wireless cards on laptops should be using NetworkManager and not initscripts on boot. Please try setting those devices to ONBOOT=no and use NetworkManager to manage wireless and wired connections. At this point, the behavior in initscripts is unlikely to change here. |