LDAP-UX Client Services B.04.10 Administrator's Guide (edition 7)

objectClass: automount
automountInformation:hostB:/tmp
automountKey:/mnt_direct/test2
The nisObject Automount Schema
The nisObject automount schema definesnisMap and nisObject structures to represent the
AutoFS maps and their entries. The AutoFS maps are stored in the LDAP directory server using
the nisMapand nisObject structures.
An Example
The following shows an example of a direct AutoFS map, auto_direct, stored in the LDAP
directory server using the nisObject automount schema:
dn:nisMapName=auto_direct,dc=nishpind
objectClass: top
objectClass: nisMap
nisMapName: auto_directdn:cn=/mnt_direct/test1,
nisMapName=auto_direct, dc=nishpind
objectClass: top
objectClass: nisObject
nisMapName: auto_direct
cn: /mnt_direct/test1
nisMapEntry:hostA:/tmp
dn:cn=/mnt_direct/test2, nisMapname=auto_direct, dc=nishpind
objectClass: top
objectClass: nisObject
nisMapName: auto_direct
cn: /mnt_direct/test2
nisMapEntry:hostB:/tmp
Limitations
The nisObject automount schema contains three attributes, cn, nisMapEntry and
nisMapName. cn is an attribute that ignores case-matching. Consider the following example:
# an indirect map named auto_test
test1 server1:/source
TEST1 server2:/source
In the above example, because the cn attribute is case-insensitive, the LDAP considers
"cn=TEST1, nisMapName=auto_test" to be a redefinition of "cn=test1,
nisMapName=auto_test".
Using the nisObject automount map schema, capital letters are not significant. In other words,
if two keys have names that are only different by the use of capital letters, then one of those
entries will be rendered inoperable because the other one is the only one that can be retrieved.
NOTE: If you use the nisObject automount map schema, do not use any keys that have
capital letters and only differ from other keys by those capital letters.
58 Installing And Configuring LDAP-UX Client Services