https://bugzilla.novell.com/show_bug.cgi?id=626515 https://bugzilla.novell.com/show_bug.cgi?id=626515#c16 --- Comment #16 from Keith Hopkins <lnxgnome@gmail.com> 2010-08-31 07:05:51 UTC --- (In reply to comment #15)
(In reply to comment #14)
I'd have to disagree with using the NIS domain as the default. Other *nix implementation use the DNS domain in preference to the NIS domain.
But who should actually do that? NFS client configurator (YaST)? Or some daemon?
assuming "some daemon" == rpc.idmapd Then the answer is 'both', and is the way things are currently implemented. idmapd has to have some value for the domain, and that is defined in the RFCs mentioned, and already implemented. Alternately, the domain is specified in a configuration, which overrides the idmapd defaults. The YaST's NFS client module can handle the manual configuration.
The question presented here is, if NIS client configurator (YaST) should offer an option to adapt /etc/imapd.conf's domain value to the current value of NIS domain. So this would not be a default behavior, just a possibility.
No, that's not quite the question presented here. It should not be the NIS domain name. The correct question here is, can/should YaST's NIS client module offer an option to configure the NFSv4 domain value (stored in /etc/imapd.conf)? A second question may be, what (if any) default value should be supplied? Hint: leave it unset, and idmapd will fall back to the FQDN of the host, minus the hostname. A third question (and possibly a separate bug) is how/where did /etc/imapd.conf get the invalid setting of "localdomain" from?
However, the problem is, if it does not mean adding extra complexity to NIS client module and if it weren't better to advice users to use NFS client module directly.
Of course, any new added code to YaST's NIS client module will add some complexity (coding, maintenance, QA, testing, etc), and that is just a fact of life. The simple alternative is just adding a text message to advise the users to go to the NFS client module and configure the NFSv4 domain name there. That would be an acceptable option IF the resources are not there to do anything better. But, isn't the whole point of YaST to make administration of the system simpler and more "user friendly"? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.