From: Ian Kent <raven@themaw.net>
To: Syed Khader <syedk@google.com>
Cc: autofs@linux.kernel.org
Subject: Re: problem with autofs
Date: Wed, 08 Nov 2006 12:12:13 +0800 [thread overview]
Message-ID: <1162959133.3555.11.camel@localhost> (raw)
In-Reply-To: <29c5cd460611071953w5c3ab139w274c75b913aee36e@mail.gmail.com>
On Wed, 2006-11-08 at 09:23 +0530, Syed Khader wrote:
> Jeff,
> It gives me
>
> dn: cn=/home,dc=testlab,dc=com
> and the automount information which i specified in the auto.home map.
>
> I think Ldap entries are fine,but the problem is to make autofs read
> from the LDAP rather than files.
No. The problem right now is to understand why the
autofs-ldap-auto-master program is not able to read the LDAP master map.
>
> Thanks,
> Abdul.
>
>
>
> On 11/8/06, Jeff Moyer <jmoyer@redhat.com> wrote:
> ==> Regarding Re: [autofs] problem with autofs; "Syed Khader"
> <syedk@google.com> adds:
>
> syedk> Hi Jeff,
> syedk> Here's the output
>
> >> ldapsearch -x -s subtree
> '(&(objectclass=automountMap)(ou=auto.master))'
>
> syedk> dn:ou=auto.master,dc=testlab,dc=com
> syedk> objectClass:top
> syedk> objectClass:automountMap
> syedk> ou:auto.master
>
> syedk> I have configured to allow anonymous bind.No ACLS are
> given
>
> OK, then what do you get with this:
>
> ldapsearch -x -s subtree -b 'ou=auto.master,dc=testlab,dc=com'
> 'objectclass=automount'
>
> -Jeff
>
next prev parent reply other threads:[~2006-11-08 4:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 16:50 problem with autofs Syed Khader
2006-11-07 8:44 ` Ian Kent
2006-11-07 13:44 ` Jeff Moyer
2006-11-07 14:12 ` Syed Khader
2006-11-07 14:47 ` Jeff Moyer
2006-11-07 15:16 ` Ian Kent
2006-11-07 15:32 ` Syed Khader
2006-11-07 16:07 ` Jeff Moyer
2006-11-07 16:20 ` Syed Khader
2006-11-07 19:01 ` Jeff Moyer
2006-11-08 3:53 ` Syed Khader
2006-11-08 4:12 ` Ian Kent [this message]
2006-11-07 15:34 ` Syed Khader
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=1162959133.3555.11.camel@localhost \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=syedk@google.com \
/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.