http://defect.opensolaris.org/bz/show_bug.cgi?id=12593
--- Comment #3 from Renee Danson Sommerfeld <renee.danson at sun.com> 2009-12-01 01:26:42 UTC --- Capturing some relevant comments from e-mail discussion: On Mon, Nov 30, 2009 at 10:22:55AM +0000, Darren Kenny wrote: > I'm easy, but I'm thinking that what is probably more > correct, is to not set the nsswitch file at all unless > the user explicitly set's a value or clicks on default > (to get the default for the 1 NS selected). > > AFAIR, if not using the GUI, the Location will usually not > have this set (it's not required if only 1 NS is selected), > and if this is the case it will fall back to the defaults > itself. > > So in some ways, our default should blank the setting (i.e. > not set an explicit value, but just let nwam handle it) - > this is probably exactly the same as if the user, selected > 1 NS, and then clicked on Default. > > As for whether having only 1 NS selected, should dynamically > change the value of the nsswitch file, as a user, I would be > quite annoyed if it kept changing the value of the file, > especially if I had one of my own already configured. I agree with all of what Darren says here. I think not having a file specified unless the user explicitly chooses one is the most intuitive approach. Darren is correct that if there is only one nameservice selected nwamd will internally choose the correct default file, so just having "default" active in those cases and not specifying a file name will work just fine, and seems simpler to me. In the case where more than one nameservice is in use, the user must specify an nsswitch file. I think in that case the GUI should simply grey out the "default" option, and require that the user specify a file before comitting. -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
