From: "Arthur Korn" <arthur@korn.ch>
To: debian-devel@lists.debian.org, autofs@linux.kernel.org
Subject: help needed for LDAP autofs master map support
Date: Mon, 27 Sep 2004 22:44:47 +0200 [thread overview]
Message-ID: <20040927204418.GA3443@turing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
Hi folks
[ debian-devel: please Cc answers to the autofs list, I'm not
subscribed ]
The new autofs 4.1.3 packages are coming along nicely, I'm
letting it in experimental until my next release to make
shure we won't end up with major errors from me in sarge. Please
try it out if you're interested in it.
Since I hardly know LDAP I need some advice on the way I should
fetch master maps from LDAP.
Debian autofs 3*-4.0.0pre10 packages (current unstable) do this
with ldapsearch. Now in 4.1.3 upstream has integrated a
dedicated tool "autofs-ldap-auto-master" from RH for this
purpose.
Now I'm unsure which of the two is the Right Thing.
Further, does autofs-ldap-auto-master merge LDIF continued
lines? (which was an issue before)
How is autofs-ldap-auto-master told where to query and what DN
to bind to? (authentication?) Debian offered variables for this
in /etc/defaults/autofs before, and I'd prefer not to break this
wrt our current stable release.
You can fetch binary and source packages from
http://packages.debian.org/experimental/utils/autofs
In the root of the source package there are still the patches
sitting which implemented LDAP master map support in stable,
they are named:
043_nsswitch_and_auto.master_in_ldap # nsswitch supported already
044_handle_ldif_continued_lines_in_init_script
Thanks in advance, 2ri
--
Secure email, spread GPG, clearsign all mail. http://www.gnupg.org
.
Why is "abbreviation" such a long word?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-09-27 20:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040927204418.GA3443@turing \
--to=arthur@korn.ch \
--cc=autofs@linux.kernel.org \
--cc=debian-devel@lists.debian.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.