Naming and Directory Services (DNS, NIS, and LDAP)

When the LDAP server has been set up, run the inityp2l script and supplyconfiguration information when prompted. inityp2l sets up the configuration andmapping files for standard and auto.* maps.1. Complete the prerequisite steps that are listed in “Prerequisites for theNIS-to-LDAP Transition” on page 234.2. On the NIS master server, become superuser or assume an equivalent role.Roles contain authorizations and privileged commands. For more informationabout roles, see “Using Role-Based Access Control (Tasks)” in System AdministrationGuide: Security Services.3. Convert the NIS master server into an N2L server.# inityp2lRun the inityp2l script on the NIS master server and follow the prompts. See“Setting Up the NIS-to-LDAP Service” on page 234 for a list of the information youneed to provide.See the inityp2l(1M) man page for more details.4. Determine if the LDAP Directory Information Tree (DIT) is fully initialized.The DIT is fully initialized if it already contains the information necessary topopulate all the maps that are listed in the NISLDAPmapping file.■ If no, continue with Step 5 and skip Step 6.■ If yes, skip Step 5 and go to Step 6.5. Initialize the DIT for the transition from the NIS source files.Perform these steps only if the DIT has not been fully initialized.a. Make sure that the old NIS maps are up-to-date.# cd /var/yp# makeFor more information, see the ypmake(1M) man page.b. Stop the NIS daemons.# svcadm disable network/nis/server:defaultc. Copy the old maps to the DIT, then initialize N2L support for the maps.# ypserv -IrWait for ypserv to exit.Tip – The original NIS dbm files are not overwritten. You can recover these files,if needed.236 System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) • January 2005