|
Bugzilla – Full Text Bug Listing |
| Summary: | Networkmanager: if on ifplugd nameresolution fails | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Danny Al-Gaaf <dalgaaf> |
| Component: | Network | Assignee: | Martin Vidner <mvidner> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | aj, yast2-maintainers |
| Version: | Alpha 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Danny Al-Gaaf
2005-11-16 20:01:14 UTC
Actually, if you switch to ifplugd, YaST should make sure that NetworkManager is stopped. I do not think that we need to change NetworkManager to check whether a device is set to "managed" or not. NetworkManager simply should not run if devices are to be managed by something else but NetworkManager. So, it looks like this need to be solved in YaST? Yes, partly. We're in discussion on how to get the who-does-network-management issue solved in a proper way. I believe this is at least partially done now. You believe this only? If the bug is fixed then please close it, if the bug is partly solved only please reassign it the appropiate maintainer which is not the default maintainer but the person familiar with NetworkManager and the problems with this tool. Let me re-assign to the yast team then. Martin, another NetworkManager related problem... YaST now uses either rcnetwork or rcnetworkmanager, since Alpha 4 IIRC. |