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

nodeInventory=*:\The third and fourth lines are the write portion of the nisplusLDAPobjectDN,and they specify where in LDAP nodeinfo data is written, as well as the rule setthat is used when nodeinfo data is deleted. In this case, create a delete rule setidentified by the database id nodeinfo_del. Because you are always writing toan existing entry in ou=Hosts, you only need to specify the object class for thenodeinfo data proper as follows.ou=Hosts,?one?objectClass=nodeInfo:\dbid=nodeinfo_delPutting it all together, our nisplusLDAPobjectDN is the following.nisplusLDAPobjectDN nodeinfo:ou=Hosts,?one?objectClass=nodeInfo,\nodeInventory=*:\ou=Hosts,?one?objectClass=nodeInfo:\dbid=nodeinfo_del5. Create the rule set that maps nodeinfo data from NIS+ to LDAP. The template(from netmasks) is the following.nisplusLDAPattributeFromColumn \netmasks: dn=("ipNetworkNumber=%s,", addr), \ipNetworkNumber=addr, \ipNetmaskNumber=mask, \description=commentThe ou=Hosts container has an additional complication in this case, as RFC 2307specifies the dn should contain the IP address. However, the IP address is notstored in the nodeinfo table, so you must obtain it in another manner.Fortunately, the crednode mapping in the template file shows how to obtain theIP address.nisplusLDAPattributeFromColumn \crednode: dn=("cn=%s+ipHostNumber=%s,", \(cname, "%s.*"), \ldap:ipHostNumber:?one?("cn=%s", (cname, "%s.*"))), \Thus, you can copy that portion of the crednode mapping. In this case, however,the cname column value is the actual host name (not the principal name), so youdo not need to extract just a portion of the cname. Making the obvioussubstitutions of attribute and column names, the nodeinfo mapping becomes thefollowing.nisplusLDAPattributeFromColumn \nodeinfo: dn=("cn=%s+ipHostNumber=%s,", cname, \ldap:ipHostNumber:?one?("cn=%s", cname)), \nodeInventory=inventory, \nodeOwner=owner6. When mapping data from LDAP to NIS+, the template netmasks entry is asfollows.286 System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) • January 2005