From: paul <paul@subsignal.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: Policy violation possible (concerns openldap/nss_ldap)
Date: Thu, 19 Jun 2003 10:55:14 -0700 [thread overview]
Message-ID: <bcrtjq$hc$1@main.gmane.org> (raw)
In-Reply-To: <871xxrb84d.fsf@nb-acer.better-com.de>
Martin Lesser wrote:
--snipped--
> So the symlink was overwritten with the vanilla configuration what - in
> our case - caused several applications which depend on ldap to not work
> properly any longer. That was really bad.
>
> How can one prevent such an IMO unacceptable behavior of overwriting
> config-files which are symlinks? Should this be seen as bug in
> gentoo/emerge?
>
> Have the changes described above to be reported as bug in nss_ldap?
>
> How can we ensure the integrity of conf-files used by more than one
> package when different packages use different locations for the *same*
> configuration (a bad thing anyway)?
>
Correct me if I'm wrong here, but AFAIK /etc/openldap/ldap.conf is used
by the openldap clients like ldapsearch ldapadd... whereas
/etc/ldap.conf is for pam_ldap and nss_ldap from PADL. They shouldn't be
the same file at all. Despite sharing some common directives such as
HOST and BASE, im not sure if the pam_ldap/nss_ldap specific options are
silently ignored by the openldap clienttools. If that is true,
/etc/openldap/ldap.conf could be overwritten by pam_ldap/nss_ldap during
install but not the other way round.
kind regards Paul
> Martin
>
> --
> gentoo-dev@gentoo.org mailing list
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-06-19 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 17:36 [gentoo-dev] Policy violation possible (concerns openldap/nss_ldap) Martin Lesser
2003-06-18 18:18 ` Donny Davies
2003-06-19 17:55 ` paul [this message]
2003-06-19 15:42 ` [gentoo-dev] " Donny Davies
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='bcrtjq$hc$1@main.gmane.org' \
--to=paul@subsignal.org \
--cc=gentoo-dev@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox