On Mon, 2008-01-07 at 08:06 +0100, Knops, Manfred wrote:
> Ian Kent wrote:
> > (...)
> > Not really a mistake. Version 5 is more strict about this but don't be
> > surprised if it starts to work again in later revisions because lot of
> > people do seem to use this even though it's not specified as valid.
> > 
> > The valid formats are ldap:[server:]dn or, more recently,
> > ldap:[//server/]dn, although the man page seems a little unclear now I
> > look at it. There are further restrictions on the dn in that it needs to
> > be either a map name alone or a full dn string including the base.
> Ok, thank you for this information. I checked the documenation on 
> opensuse 10.3. They use version 5.0.2. And they wrote:

OK, there's nearly 50 patches going into 5.0.3, maybe more by the time
it gets released so it's going to be a bit hard to work out what's going
on.

We usually get most useful information from debug logs.
See http://people.redhat.com/jmoyer for instructions to collect it.
Ensure that daemon.* is actually being logged.

> 
> dn: cn=/mounts,nisMapName=auto.master,ou=AUTOFS,dc=example,dc=org
> objectClass: nisObject
> nisMapName: auto.master
> cn: /mounts
> nisMapEntry: ldap 
> ldapserver.example.org:nisMapName=auto.mounts,ou=AUTOFS,dc=example,dc=org


> 
> So I will try to use ldap://server/dn on opensuse to make ldap 
> replication possible.
> 
> > (...)
> > Does this same connection information work OK for ldapsearch?
> Yes, it works.
> [EMAIL PROTECTED] ~]# ldapsearch -v "(objectClass=automountMap)"
> ldap_initialize( <DEFAULT> )
> SASL/DIGEST-MD5 authentication started
> Please enter your password:
> SASL username: ldap
> SASL SSF: 128
> SASL installing layers
> filter: (objectClass=automountMap)
> requesting: All userApplication attributes
> # extended LDIF
> #
> # [EMAIL PROTECTED] ~]# ldapwhoami -U ldap -X u:ldap
> SASL/DIGEST-MD5 authentication started
> Please enter your password:
> SASL username: u:ldap
> SASL SSF: 128
> SASL installing layers
> dn:uid=ldap,ou=users,dc=abaqus,dc=de
> Result: Success (0)
> 
> # base <> with scope subtree
> # filter: (objectClass=automountMap)
> # requesting: ALL
> #
> 
> # auto.home, automount, abaqus.de
> dn: automountMapName=auto.home,ou=automount,dc=abaqus,dc=de
> objectClass: top
> objectClass: automountMap
> automountMapName: auto.home
> description: This chapter is analog to /etc/auto.home
> 
> # auto.master, automount, abaqus.de
> dn: automountMapName=auto.master,ou=automount,dc=abaqus,dc=de
> objectClass: top
> objectClass: automountMap
> automountMapName: auto.master
> description: This chapter is analog to the file /etc/auto.master
> 
> # search result
> search: 3
> result: 0 Success
> 
> # numResponses: 3
> # numEntries: 2
> 
> 
> 
> testsaslauthd also works fine:
> [EMAIL PROTECTED] ~]# testsaslauthd -u ldap -p ldap
> 0: OK "Success."
> 
> 
> 
> ldapwhoami also works fine:
> [EMAIL PROTECTED] ~]# ldapwhoami -U ldap -X u:ldap
> SASL/DIGEST-MD5 authentication started
> Please enter your password:
> SASL username: u:ldap
> SASL SSF: 128
> SASL installing layers
> dn:uid=ldap,ou=users,dc=abaqus,dc=de
> Result: Success (0)
> 
> 
> It also work for automount. Because /net mount with /etc/auto.net works:
> Jan  4 09:35:19 kerberos automount[18890]: mounted indirect mount on 
> /net with timeout 60, freq 15 seconds
> 
> He got this information from ldap:
> [EMAIL PROTECTED] ~]# ldapsearch 
> "(&(objectClass=automount)(automountKey=/net))" -LLL
> SASL/DIGEST-MD5 authentication started
> Please enter your password:
> SASL username: ldap
> SASL SSF: 128
> SASL installing layers
> dn: 
> automountKey=/net,automountMapName=auto.master,ou=automount,dc=abaqus,dc=de
> objectClass: top
> objectClass: automount
> automountKey: /net
> automountInformation: /etc/auto.net --timeout=60
> 
> He also notice that /home are a mount point. He found this information 
> in ldap. So he got a connection. But he doesn't read the mount options:
> Jan  4 09:35:19 kerberos automount[18890]: mount_autofs_indirect: failed 
> to read map for /home

I didn't see the master map entry for the auto.home map or any entries
for it above.

Might be a good idea to post all the actual (or carefully edited for
privacy) maps to give a full overview and of course the debug log so we
can see what is happening.

Ian


_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs

Reply via email to