On Thu, 2008-01-03 at 16:28 +0100, Knops, Manfred wrote: > Knops, Manfred wrote: > > (...) > > # /home, auto.master, automount, abaqus.de > > dn: > > automountKey=/home,automountMapName=auto.master,ou=automount,dc=abaqus,dc=de > > objectClass: top > > objectClass: automount > > automountKey: /home > > automountInformation: ldap > > 192.168.1.2:automountMapName=auto.home,ou=automount,dc=abaqus,dc=de > > --timeout=60 > [EMAIL PROTECTED] ~]# tail /tmp/automount.ldif > dn: > automountKey=/home,automountMapName=auto.master,ou=automount,dc=abaqus,dc=de > objectClass: top > objectClass: automount > automountKey: /home > automountInformation: > ldap://192.168.1.2/automountMapName=auto.home,ou=automount,dc=abaqus,dc=de > > I found one mistake by myself. I changed the automountInformation for /home. > I changed from "ldap 192.168.1.2:auto..." to "ldap://192.168.1.2/auto...";.
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. > > Now I have a sasl problem. > Jan 3 16:18:55 hostB automount[12904]: Starting automounter version > 5.0.1-31, master map auto.master > Jan 3 16:18:55 hostB automount[12904]: using kernel protocol version 5.00 > Jan 3 16:18:55 hostB automount[12904]: No worthy mechs found > Jan 3 16:18:55 hostB automount[12904]: sasl_bind_mech: sasl_client > start failed with error: SASL(-4): no mechanism available: No worthy > mechs found > Jan 3 16:18:55 hostB automount[12904]: lookup_init: lookup(ldap): > cannot initialize authentication setup > Jan 3 16:18:55 hostB automount[12904]: mount_autofs_indirect: failed to > read map for /home > Jan 3 16:18:55 hostB automount[12904]: handle_mounts: mount of /home > failed! > Jan 3 16:18:55 hostB automount[12904]: master_do_mount: failed to > startup mount > Jan 3 16:18:55 hostB automount[12904]: mounted indirect mount on /net > with timeout 60, freq 15 seconds > Jan 3 16:18:55 hostB automount[12904]: ghosting enabled > Jan 3 16:19:56 hostB automount[12904]: attempting to mount entry /net/gnome > Jan 3 16:19:56 hostB automount[12904]: mounted /net/gnome > Jan 3 16:20:09 hostB automount[12904]: mount still busy /net > Jan 3 16:20:40 hostB last message repeated 2 times > Jan 3 16:21:11 hostB last message repeated 2 times > Jan 3 16:21:26 hostB automount[12904]: expiring path /net/gnome > Jan 3 16:21:26 hostB automount[12904]: umounted offset mount > /net/gnome/backup/opt-abaqus/server > Jan 3 16:21:26 hostB automount[12904]: expired /net/gnome > > If someone has an idea, please feel free to help me. Does this same connection information work OK for ldapsearch? Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
