LDAP-UX Client Services B.04.15 Administrator's Guide

2.10.2.1.1 Schema
The following shows the RFC 2307-bis automount schema in the LDIF format:
objectClasses:
( 1.3.6.1.1.1.2.16 NAME 'automountMap' DESC 'Automount Map information'
SUP top STRUCTURAL MUST automountMapName MAY description X-ORIGIN
'user defined' ) objectClasses: ( 1.3.6.1.1.1.2.17 NAME 'automount'
DESC 'Automount information' SUP top STRUCTURAL MUST ( automountKey
$ automountInformation ) MAY description X-ORIGIN 'user defined'
) attributeTypes: ( 1.3.6.1.1.1.1.31 NAME 'automountMapName' DESC
'automount Map Name' EQUALITY caseExactIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26
SINGLE-VALUE X-ORIGIN 'user defined' ) attributeTypes: ( 1.3.6.1.1.1.1.32
NAME 'automountKey' DESC 'Automount Key value' EQUALITY caseExactIA5Match
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE X-ORIGIN 'user
defined' ) attributeTypes: ( 1.3.6.1.1.1.1.33 NAME 'automountInformation'
DESC 'Automount information' EQUALITY caseExactIA5Match SYNTAX
1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE X-ORIGIN 'user defined'
)
For Netscape Directory Server, each entry started by "attributetypes:" or "objectclasses:"
must be one continuous line.
2.10.2.1.2 An Example
The following shows an example of a direct AutoFS map, auto_direct, stored in the LDAP
directory server using new automount schema:
dn:automountMapName=auto_direct,dc=nishpind
objectClass: top objectClass: automountMap automountMapName: auto_direct
dn:automountKey=/mnt_direct/test1,\ automountMapname=auto_direct,
dc=nishpind objectClass: top objectClass: automount automountInformation:hostA:/tmp
automountKey: /mnt_direct/test1
dn:automountKey=/mnt_direct/test2,\
automountMapname=auto_direct, dc=nishpind objectClass: top objectClass:
automount automountInformation:hostB:/tmp automountKey:/mnt_direct/test2
2.10.2.2 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.
2.10.2.2.1 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
2.10.2.2.2 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.
2.10 AutoFS Support 53