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

nisplusLDAPdatabaseIdMappingIf this name resides under the domain name specified by thenisplusLDAPbaseDomain attribute, you can omit the portion that equals thenisplusLDAPbaseDomain value.For example, if nisplusLDAPbaseDomain has the value some.domain., and theobject to be mapped is a table called nodeinfo.some.domain., the object namecan be shortened to nodeinfo.2. Invent a database id to identify the object.The database id must be unique for the mapping configuration used, but is nototherwise interpreted. It does not show up in the LDAP data. In order to reduceconfusion with entry object mappings, create a database id identifying the tableobject proper (not the table entries) using an explanatory string like _table at theend.For this example, use the database id nodeinfo_table, and establish theconnection between the database id and the object in the standard mapping filelocation (/var/nis/NIS+LDAPmapping) by adding the following.nodeinfo_table:nodeinfo.some.domain.Assuming that nisplusLDAPbaseDomain is some.domain., the followingwould also work.nisplusLDAPdatabaseIdMappingnodeinfo_table:nodeinfo3. Decide on a TTL for the object.This is the time during which the rpc.nisd daemon regards its local copy of theobject as valid. When the TTL expires, the next reference to the object will initiatean LDAP lookup to refresh the object.There are two different TTL values. The first is set when the rpc.nisd daemonfirst loads the object from disk (after a reboot or restart), and the second pertains toall refreshes from LDAP. The first TTL is selected randomly from a configuredrange. For example, if nodeinfo_table should be valid for a period of betweenone and three hours following initial load, and for twelve hours thereafter, specifythe following.nisplusLDAPentryTtlnodeinfo_table:3600:10800:432004. Decide where the object data should be stored in LDAP.The template mapping file suggests putting non-entry object data in theou=nisPlus container.If you use this scheme, and have not yet created the appropriate attribute, objectclass, and container, see “Mapping NIS+ Objects Other Than Table Entries”on page 273.For example, assume you want to store the nodeinfo object in theou=nisPlus,dc=some,dc=domain container, and that the LDAP entry shouldhave the cn nodeinfo. Create the following nisplusLDAPobjectDN.nisplusLDAPobjectDN nodeinfo_table:\cn=nodeinfo,ou=nisPlus,dc=some,dc=domain?base?\objectClass=nisplusObjectContainer:\Chapter 16 • Transitioning From NIS+ to LDAP 283