Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • I understand the necessity for root to remain local. So, you are stating that a NIS server should have a normal Linux configuration, with users in both /etc/passwd and /etc/shadow (and shadow passwords in the latter)? And a NIS client? How can the shadow be avoided, following the guide? Ok, you suggest to use NIS+, but I've read it is completely different from NIS. Maybe is it not completely true? Commented Jan 15, 2015 at 9:40
  • 1
    @BowPark Personally, I don't use NIS+, I use OpenLDAP/Kerberos so I can't answer that question for you. However, to answer the first question: yes, your NIS server will be will be like a regular machine and all of the users and passwords are stored in /etc/passwd and /etc/shadow. Do not merge them as any modernish linux (>2.4) will be able to handle /etc/shadow passwords and will have pam(8). If you have to merge them then use unshadow(8), but I'd just skip those instructions. Commented Jan 15, 2015 at 16:54
  • So, for the clients you would simply ignore that instructions (the advices about avoiding shadow in the 2003-guide)? I agree(d) with you, but the fact is that the client doesn't work! Maybe this system is too old. Commented Jan 15, 2015 at 16:58
  • For the clients, you only need the following: 1) edit /etc/yp.conf 2) edit /etc/nssswitch.conf 3) start ypbind. At least that is what my notes say from 2011. Commented Jan 15, 2015 at 17:22
  • @BowPark For the clients, you only need the following: 1) edit /etc/yp.conf 2) edit /etc/nssswitch.conf 3) start ypbind. At least that is what my notes say from 2011. Commented Jan 16, 2015 at 16:08