Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
one computer is fine. the two really having nothing to do with each other, more a coincidental solution using multiple technologies.
the user would matter, that's the point. as the user only exists on the nis service itself, that user can log in anywhere and all files on the *shared* /home/username directory will already be owned by that user.
generally ldap has replaced nis+ these days, if you're in a green field location, ldap is much more modern and extensible. lots of software, appliances etc, can hook directly into LDAP, but not NIS+.
Distribution: Fedora 7, Fedora 9, Solaris 10, Mac OS X, RHEL5
NFS and NIS
Thanks for the answer. Now I have other question:
What should I do, if I want the users to share files with NFS (controlling the user access to files, permissions ...) but I want them to store their documents and run their applications in their own computers?
Can I do this with LDAP?
I think it is not necessary that the users can login in any machine of the network, having this in mind I don't need NIS, am I right?
you can't "do it" with ldap, it's really not related, as above, it's a coincidental end result, not a feature of anything... if you don't want a centralized /home then don't provide one over nfs. ldap will, along with *any* valid user-base definition mechanism (including files, nis, nis+ and many others) provide a home directory attribute. That merely coincides with the fact that NFS might mount a centralized /home is unknown to that.