Installing And Configuring LDAP-UX Client Services

AutoFS Support

Step 3. Delete the following two entries in the /var/opt/netscape/servers/slapd-<server-instance>/ \ config/schema/10rfc2307.ldif file. These two entries contain the ‘automountInformation’ attributetype and the ‘automount’ objectclass. The data in these two entries define the obsolete automount schema. The complete two entries are:

•attributeTypes:( 1.3.6.1.1.1.1.25 NAME ’automountInformation’ DESC ’Standard LDAP attribute type’ SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 X-ORIGIN ’RFC 2307’)

•objectClasses:( 1.3.6.1.1.1.2.9 NAME ’automount’ DESC ’Standard LDAP objectclass’ SUP top MUST (cn $automountInformation)MAY (description) X-ORIGIN ’RFC2307’)

Step 4. Restart the daemon, slapd. This is to ensure that the updated schema file is recognized by the Netscape Directory Server.

/var/opt/netscape/servers/slapd-<server-instance>/restart-slap d

For example:

/var/opt/netscape/servers/slapd-ldapA.cup.hp.com/restart-slapd

After you delete the obsolete automount schema, you must re-run the setup program to import the new automount schema into the LDAP directory server.

Attribute Mappings

LDAP-UX Client Services B.04.00 supports attribute mappings between the new RFC 2307-bis automount schema and the nisObject automount schema. This feature allows the directory administrators to use the nisObject schema if they have already deployed it.

When both new automount schema and nisObject schema exist in the LDAP directory server, if you choose to use the nisObject automount schema, you must run the setup program using the custom configuration to perform the attribute mappings and search filter changes for the automount service. The attribute mappings include the following:

•Remap the new automount attributes to the nisObject automount attributes. The attribute mappings are done in step 10 of the Custom Configuration. For detailed information on how to remap the automunt attributes, see “Custom Configuration” on page 34.

60

Chapter 2