https://bugs.openldap.org/show_bug.cgi?id=8341
--- Comment #9 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Re25:
• 2a537ad0
by OndÅ™ej KuznÃk at 2021-09-14T16:17:45+00:00
ITS#8341 Allow normalised values for namingContexts in cn=monitor
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8341
--- Comment #8 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE26:
• ea92405a
by OndÅ™ej KuznÃk at 2021-09-14T16:17:25+00:00
ITS#8341 Allow normalised values for namingContexts in cn=monitor
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8341
--- Comment #7 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
• bfe3d19e
by OndÅ™ej KuznÃk at 2021-09-09T10:26:06+01:00
ITS#8341 Allow normalised values for namingContexts in cn=monitor
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6467
--- Comment #11 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE25:
commit a00ec090bdcdfdb390ace2238f581ad147e5974f
Author: OndÅ™ej KuznÃk <ondra(a)mistotebe.net>
Date: Tue Jun 1 13:56:58 2021 +0100
ITS#6467 Free uuid list after we're finished
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6467
--- Comment #10 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
commit 726a2031334d066a6e463d7b992b6ca7b390e631
Author: OndÅ™ej KuznÃk <ondra(a)mistotebe.net>
Date: Tue Jun 1 13:56:58 2021 +0100
ITS#6467 Free uuid list after we're finished
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9571
Issue ID: 9571
Summary: Add Behera Draft 8 compatibility flag to ppolicy
overlay
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: mhardin(a)symas.com
Target Milestone: ---
The RFC for Behera Password Policy, Draft, 10 changes modification semantics of
certain policy attributes from those that were in effect in Draft 8. To
preserve compatibility with applications that depend on the Draft 8 semantics,
a compatibility flag needs to be added to the ppolicy configuration that
restores the Draft 8 semantics.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8962
--- Comment #5 from Mehmet gelisin <mehmetgelisin(a)aol.com> ---
master:
Commits:
• 0ae71baf
by Howard Chu at 2021-07-13T12:10:28+01:00
ITS#9608 fix delete of nonexistent sessionlog http://www-look-4.com/
RE25:
Commits:
• 11e0c783
by Howard Chu at 2021-07-13T15:04:31+00:00
ITS#9608 fix delete of nonexistent sessionlog
http://www.compilatori.com/
RE24:
Commits:
• db23304b
by Howard Chu at 2021-07-13T15:05:36+00:00
ITS#9608 fix delete of nonexistent sessionlog http://www.wearelondonmade.com/
master:
Commits:
• 0ae71baf
by Howard Chu at 2021-07-13T12:10:28+01:00 http://www.jopspeech.com/
ITS#9608 fix delete of nonexistent sessionlog
RE25:
Commits:
• 11e0c783 http://joerg.li/
by Howard Chu at 2021-07-13T15:04:31+00:00
ITS#9608 fix delete of nonexistent sessionlog
RE24: http://connstr.net/
Commits:
• db23304b
by Howard Chu at 2021-07-13T15:05:36+00:00
ITS#9608 fix delete of nonexistent sessionlog
master:
Commits:
• 0ae71baf
by Howard Chu at 2021-07-13T12:10:28+01:00
ITS#9608 fix delete of nonexistent sessionlog http://embermanchester.uk/
RE25:
Commits:
• 11e0c783
by Howard Chu at 2021-07-13T15:04:31+00:00
ITS#9608 fix delete of nonexistent sessionlog
http://www.slipstone.co.uk/
RE24:
Commits:
• db23304b
by Howard Chu at 2021-07-13T15:05:36+00:00
ITS#9608 fix delete of nonexistent sessionlog
http://www.logoarts.co.uk/
but unfortunatley the FAQ software breaks Apache when you try and
delete an answer. I think the better solution is just to remove the FAQ
software completely.
I experimented a bit with a service file. It seems to work well with
either Type=forking and NotifyAccess=all, or Type=notify and
http://www.acpirateradio.co.uk/
ExecStart=slapd -d none. The latter (disabling forking) is definitely
what systemd upstream recommends.
In either case, MAINPID= didn't actually seem to help anything.
NotifyAccess=main has a chicken-and-egg problem, because systemd needs
to know the main PID in order for us to send it the message containing
the PID! :) I think the only reasonable way to leave forking enabled
https://waytowhatsnext.com/
would be to also require a PIDFile= setting, which solves that problem.
But I'd rather sidestep the entire thing, omit MAINPID= as well, and
Looking at the systemctl output I still think STATUS= is redundant and
could be omitted.
https://www.webb-dev.co.uk/
So I guess my recommendation for the notify call boils down to:
rc = sd_notify( 1, "READY=1" );
and a slapd.service along the lines of:
[Unit]
Description=OpenLDAP server
[Service]
Type=notify
ExecStart=%LIBEXECDIR%/slapd -h 'ldap:/// ldapi:///' -d0
[Install]
WantedBy=multi-user.target
(basically identical to the example in systemd.service(5).)
Side note: the version message from slapd appears in the journal twice,
once with the timestamp and once without...
I experimented a bit with a service file. It seems to work well with
either Type=forking and NotifyAccess=all, or Type=notify and
ExecStart=slapd -d none. The latter (disabling forking) is definitely
what systemd upstream recommends.
In either case, MAINPID= didn't actually seem to help anything.
NotifyAccess=main has a chicken-and-egg problem, because systemd needs
to know the main PID in order for us to send it the message containing
the PID! :) I think the only reasonable way to leave forking enabled
http://www.iu-bloomington.com/
would be to also require a PIDFile= setting, which solves that problem.
But I'd rather sidestep the entire thing, omit MAINPID= as well, and
Looking at the systemctl output I still think STATUS= is redundant and
could be omitted.
--
You are receiving this mail because:
You are on the CC list for the issue.