Bug 459120 - NM_CONTROLED default value
Summary: NM_CONTROLED default value
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 438902
TreeView+ depends on / blocked
 
Reported: 2008-08-14 15:03 UTC by Jiri Moskovcak
Modified: 2015-02-01 22:48 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-08-14 18:10:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jiri Moskovcak 2008-08-14 15:03:15 UTC
Description of problem:
NetworkManager takes control over device even if NM_CONTROLED= is not set. The default value for other settings in ifcfg-* scripts is 'no' so it should be the same for NM.

Comment 1 Dan Williams 2008-08-14 18:10:57 UTC
This is by design.  NM will only treat a device as unmanaged if NM_CONTROLLED=no is specified in the ifcfg.  What's the real problem here?  The defaults don't need to be consistent (and some aren't, like PEERDNS defaults to yes).

Comment 2 Jiri Moskovcak 2008-08-15 08:51:53 UTC
The problem is if someone creates ifcfg-* file by hand without any mention of NM he can be confused why NM is taking control over the card. So I think better solution would be to make anaconda to write NM_CONTROLLED=yes into config files and make deafult 'no'.

Jirka


Note You need to log in before you can comment on or make changes to this bug.