Bugzilla – Bug 100205
incomplete nsswitch.conf when selecting NIS
Last modified: 2005-08-26 10:23:19 UTC
During installation, I selected NIS as the configuration method. I would expect yast to include nis lookups at least for the hosts and automount targets in nsswitch.conf. I remember this used to be the default behavior in previous products.
Please don't add NIS lookups for hosts per default. Maybe add a button, but you should really setup a local nameserver (maybe with help of YaST2). What we should change per default is: Make sure passwd and group uses compat or "files nis" services: files nis netgroup: nis automount: files nis aliases: files nis
If this used to be a default, it has to be long time ago (I cannot find such thing in the code of 8.0 and I haven't looked to older one). Anyway - this is a feature request. Thorsten, please add it to FD.
I don't agree that this is a new feature, at least the four entries are a bug, even if nobody has reported that.
Well, ok - it could be changed easily. Does the same change apply also for ldap? And which value should they have if nis is unset - just "files" for all of them?
I think automount in the above list is wrong, we should already handle that (at least it seems so since it always works). (In reply to comment #4) > Does the same change apply also for ldap? I don't think that somebody is using services in LDAP, but changing it does not break anything. netgroup and aliases should be changed for LDAP, too. > And which value should they have if nis is unset - just "files" for all of them? Yes, just remove nis.
Ah, there's that old conflict between nis and ldap. Situation: ldap enabled (thus services, netgroup, aliases have "files ldap" value). When I enable nis using yast2-nis-client, should I only add "nis" value to those maps or rahter replace it directtly with "files nis" values?
For beta1, I fixed the nis-client that "replace" way (using "files nis", whatever there was before). But ldap-client stil has only adding "ldap".
I think adding is more the correct way. If ldap is still enabled, I think there are reasons for it. If it was disabled, it does not harm.
But LDAP is not enabled any more; when enabling NIS, the values of passwd_compat etc. are removed and vice versa - see bug #51981.
Uhm, Thorsten - do you agree? With current behaviour, the solution from #8 would lead to inconsistencies in /etc/nsswitch.conf I would like to change also yast2-ldap-client to "replace" behaviour.
Then replace it.
done