|
Bugzilla – Full Text Bug Listing |
| Summary: | Switching to NetworkManager, NIS is gone | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Karl Eichwalder <ke> |
| Component: | YaST2 | Assignee: | Bin Li <bili> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | kukuk |
| Version: | Factory | ||
| Target Milestone: | RC 2 | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Documentation | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Karl Eichwalder
2010-05-25 14:14:50 UTC
resolv.conf has nothing to do with NIS. Using NIS with NetworkManager is and never was a valid usecase. What does "no longer works" mean? Any error messages, anything in the log files, ...? If NM does not work in a NIS environment, yast must at least warn, if the user on a NIS client machine tries to switch from "Traditional Method with ifup" to "User Controlled with NetworkManager" and we must add some such warning to our docs. The nis was not in Factory now, I'll submit it later. I mean the patch for NIS in NetworkManager. I've commit the NIS support in NM.
41285 State:new By:BinLi When:2010-06-09T13:24:44
submit: home:BinLi:branches:GNOME:Factory/NetworkManager -> GNOME:Factory
Descr: NIS support and update resolv.conf once(bnc#608677, bnc#595708,
bnc#544195, bnc#537907)
Fixed. Thanks for your report. This is an autogenerated message for OBS integration: This bug (608677) was mentioned in https://build.opensuse.org/request/show/41997 11.3 / NetworkManager |