From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: openldap: update to 2.4.53.
Date: Tue, 08 Sep 2020 08:14:59 +0200 [thread overview]
Message-ID: <20200908061459.lR3qqJVf52MVqvTfcM4A4Fs7q-z6iP9cJrscpY93vx8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24750@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/24750#issuecomment-688641856
Comment:
@CameronNemo yes that would work since the file needs to be renamed to "DB_CONFIG" for berkeleydb to open it.
That said, I'm not entirely sure it would be a good idea to remove it, since if anyone wants to customize this, it really needs to be in `/var/lib/openldap/openldap-data/` (or wherever slapd.conf ``directory`` directive points to) to take effect, and not in `/etc/openldap`, which can be confusing (especially since it will be silently ignored by bdb).
Also, note that the installer makefile intentionally places DB_CONFIG.example with 600 perms in `/var/lib/openldap/openldap-data/` while the one in the examples dir is world-readable. If anyone customizes this, after the first hurdle of discovering that it should placed in `/var/lib/openldap/openldap-data/` rather than `/etc/openldap`, will most certainly just copy it from the examples, and leave it world-readable. So this wouldn't be a good default.
next prev parent reply other threads:[~2020-09-08 6:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 22:54 [PR PATCH] " ailiop-git
2020-09-08 2:02 ` CameronNemo
2020-09-08 2:03 ` CameronNemo
2020-09-08 2:16 ` CameronNemo
2020-09-08 6:14 ` ailiop-git [this message]
2020-10-17 9:51 ` [PR PATCH] [Updated] " ailiop-git
2020-10-31 20:01 ` ailiop-git
2020-11-15 18:44 ` ailiop-git
2020-11-15 19:02 ` ailiop-git
2021-02-15 5:03 ` [PR PATCH] [Merged]: " ericonr
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=20200908061459.lR3qqJVf52MVqvTfcM4A4Fs7q-z6iP9cJrscpY93vx8@z \
--to=ailiop-git@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).