Description of problem:
when using ldap for distributung nfs mounts, autofs 4.1.0-2
will not be able to resolve the correct mount points and
therefore automountd can't handle these mount points.

here's my log from /var/log/mesages and my ldap 
server's  /var/log/slpad.log:

==> /var/log/slapd.log <==
Mar 18 16:44:09 theseus slapd[29091]: daemon: conn=103 fd=14 
connection from IP=192.168.15.11:40753 (IP=0.0.0.0:389) acc
epted.
Mar 18 16:44:09 theseus slapd[29091]: conn=103 op=0 BIND dn="" 
method=128
Mar 18 16:44:09 theseus slapd[29091]: conn=103 op=0 RESULT tag=97 
err=0 text=

==> /var/log/messages <==
Mar 18 16:44:09 theseus automount[30788]: using timeout 300 seconds; 
freq 75 secs
Mar 18 16:44:09 theseus automount[30788]: lookup(ldap): query failed 
for (&(objectclass=nisObject))
Mar 18 16:44:10 theseus automount[30788]: lookup(ldap): query failed 
for (&(objectclass=automount))
Mar 18 16:44:10 theseus automount[30788]: failed to load map, exiting
Mar 18 16:44:10 theseus automount[30788]: failed to remove dir 
`^W^E^Hâ^V]Ã^P: No such file or directory


as you can see in slapd.log there's >>> BIND dn="" <<< which normally
should be resolved/mapped to >>> 
dn="NISMAPNAME=AUTO.HOME,OU=SERVICES,DC=BL,DC=MAJOX,DC=DE" <<<

that's why automount can't load the maps tells "No such file or 
directory" referring to a file/dirname that seems to be real ugly
memory data 


Version-Release number of selected component (if applicable): 4.1.0-2


How reproducible:
1) install ldap server
2) create automount map entries within ldap server
3) try using these entries with installed autofs 4.1.0-2 



Workaround:
deinstall autofs 4.1.0-2 and install autofs-3.1.7-36 (is used the
rpm from redhat 9.0) and everything works fine...