Description of Problem:
"nisplus" is virtually never used, but always in /etc/nsswitch.conf. Why?
Couldn't we eliminate the overhead of referencing nisplus for the 99.99% of
machines that don't use it? For that matter, could we add "nisplus nis" _only_
NIS is enabled via authconfig? This seems like it addresses more of the
authentication scenerios, more of the time.
Version-Release number of selected component (if applicable):
Milan, beta 2
authconfig will add NIS to nsswitch.conf, but because it can not configure
nisplus, it leaves nisplus in nsswitch.conf if it finds it there.
I understand that authconfig will leave nisplus there if its *already* there...
this is as it should be. My argument is against it being there by default. If
someone adds it, sure: leave it there.
But... if nisplus can't be configured in any other way than manually, why not
have the administrator configure the machine for nisplus and add "nisplus" to
nsswitch.conf themselves. Since we can't setup nisplus through authconfig, why
do the first 5% of the job ourselves, when %99.99 percent of RHL machines will
pay a small penality because of it?
If we are already telling NIS+ admins that they have to set it up themselves...
we wouldn't really inconvenience them by not adding a step that we shouldn't be
doing for the vast majority of machines anyway.
Shouldn't authconfig at least allow checking whether or not to use NIS+ and
tell what needs to be done to configure NIS+?
The new beta still has the same issue... why list it if has to be setup manually
At least the current release doesn't use use nisplus anymore. Therefore I close