System information

This last example works as expected because auto fs does not include the contents of a file map of

the same name as the one it is reading. As such, auto fs moves on to the next map source in the

nsswi tch configuration.

9.4 .4 . Using LDAP t o St ore Aut omount er Maps

LDAP client libraries must be installed on all systems configured to retrieve automounter maps from

LDAP. On Red Hat Enterprise Linux, the o penl dap package should be installed automatically as a

dependency of the auto mo unter. To configure LDAP access, modify

/etc/o penl d ap/l d ap. co nf. Ensure that BASE, URI, and schema are set appropriately for your

site.

The most recently established schema for storing automount maps in LDAP is described by

rfc230 7bi s. To use this schema it is necessary to set it in the auto fs configuration

(/etc/sysco nfi g /auto fs) by removing the comment characters from the schema definition. For

example:

Examp le 9 .4 . Set t in g au t o f s co n f ig u rat io n

DEFAULT_MAP_OBJECT_CLASS="automountMap"

DEFAULT_ENTRY_OBJECT_CLASS="automount"

DEFAULT_MAP_ATTRIBUTE="automountMapName"

DEFAULT_ENTRY_ATTRIBUTE="automountKey"

DEFAULT_VALUE_ATTRIBUTE="automountInformation"

Ensure that these are the only schema entries not commented in the configuration. The

auto mo untKey replaces the cn attribute in the rfc230 7bi s schema. An LD IF of a sample

configuration is described below:

Examp le 9 .5. LDF co n f ig u rat io n

# extended LDIF

# LDAPv3

# base <> with scope subtree

# filter: (& (objectclass=automountMap)(automountMapName=auto.master))

# requesting: ALL

# auto.master, example.com

dn: automountMapName=auto.master,dc=example,dc=com

objectClass: top

objectClass: automountMap

automountMapName: auto.master

# extended LDIF

# LDAPv3

# base <automountMapName=auto.master,dc=example,dc=com> with scope

subtree

# filter: (objectclass=automount)

# requesting: ALL

⁠Chapt er 9 . Net work File Syst em (NFS)