All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Largent <jlargent@imagelinks.com>
To: linux-admin@vger.kernel.org
Subject: Autofs & LDAP
Date: Tue, 17 Feb 2004 13:13:23 -0500	[thread overview]
Message-ID: <403259C3.6060600@imagelinks.com> (raw)

On Redhat 7.3 with openldap-servers-2.0.27-2.7.3, and autofs-3.1.7-28. I have a
working autofs/ldap configuration.

dn: ou=auto.master,dc=il,dc=com
ou: auto.master
objectClass: top
objectClass: automountMap

dn: cn=/opt,ou=auto.master,dc=il,dc=com
objectClass: automount
cn: /opt
automountInformation: ldap:ldap.il.com:ou=auto.opt,dc=imagelinks,dc=com

dn: cn=bin,ou=auto.opt,dc=il,dc=com
objectClass: automount
cn: bin
automountInformation: -ro bserv.il.com:/export/Linux-2/opt/bin

The same maps on Fedora core 1 with openldap-servers-2.1.22-8, and 
autofs-3.1.7-42 refuse to work.

This is what I see in the logs:
automount[13734]: starting automounter version 3.1.7, path = /cm, maptype = 
ldap, mapname = ldap.il.com:ou=auto.cm,dc=il,dc=com

if I put a space between the : after the ldap hostname and the dn auto fs 
reconizes the automount but then fails on the lookup.
automount[8400]: lookup(ldap): query failed for (&(objectclass=automount)(cn=opt))

a ldapsearch -x "(&(objectclass=automount)(cn=opt))" returns the proper map.

Any suggestions??
In slapd.conf I have "allow bind_v2"



-- 
Jeff Largent                   ImageLinks, Inc.


             reply	other threads:[~2004-02-17 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17 18:13 Jeff Largent [this message]
2004-02-23 21:53 ` Autofs & LDAP Jeff Largent
  -- strict thread matches above, loose matches on Subject: below --
2008-09-21 21:40 autofs+LDAP Mikel Jimenez
2008-09-22  4:35 ` autofs+LDAP Ian Kent
2008-09-22  7:36   ` autofs+LDAP Mikel Jimenez
2008-09-22 11:12     ` autofs+LDAP Ian Kent
2008-09-22 16:33   ` autofs+LDAP Douglas E. Engert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=403259C3.6060600@imagelinks.com \
    --to=jlargent@imagelinks.com \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.