NIS/LDAP Gateway Administrator's Guide

1. On an NIS client system, log in as root and change the domain by editing the file
/etc/rc.config.d/namesvrs. Change the line containing NIS_DOMAIN to:
NIS_DOMAIN=test-ldap
2. On the same NIS client system logged in as root, restart the NIS client process:
/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start
3. Use the ll(1) command to examine any files and make sure the owner and group of each file
are accurate:
ll /tmp
If any owner or group shows up as a number instead of a user or group name, respectively,
the NIS/LDAP Gateway is not functioning properly.
4. Create a new file and change the file's owner to another user:
cd /tmp
touch file
chown newuser file
ll file
where newuser is the name of a different user. The final ll(1) command should display the
file owned by the new user.
5. Log in to the client system as an ordinary user, that is, a non-root user, in the directory and
not in /etc/passwd. If this fails, see “Troubleshooting”.
6. Once you've logged in as an ordinary user, check to see if your NIS/LDAP Gateway is serving
the NIS client by giving the following command on the client system:
domainname
7. Display one of your maps with a command like the following:
ypcat group | more
8. Repeat steps 3 and 4 above logged in as an ordinary user.
Put the NIS/LDAP Gateway into Production
This section describes how you can put the NIS/LDAP Gateway into production in your
environment, after you've completed all the verification and testing you need, determined how
you will administer your directory, and informed your user community about the change. You
can stop each NIS server and start the NIS/LDAP Gateway server, one system at a time, completing
each subnet one at a time. Modify these commands as needed for your environment.
1. If you decide to use ldappasswd, install it on the appropriate systems.
2. Install the NIS/LDAP Gateway on an NIS server.
3. Copy the ypldapd.conf file from another NIS/LDAP Gateway server. Modify it, if necessary,
for example if you have multiple directory servers to distribute the load among or to set the
domain to your production domain. See “Configuration Parameters” for details.
4. Stop the NIS server daemon on your NIS server system. Log in to the server as root and
enter the following command:
/sbin/init.d/nis.server stop
Put the NIS/LDAP Gateway into Production 25