https://bugs.openldap.org/show_bug.cgi?id=8227
--- Comment #4 from Ondřej Kuzník <ondra(a)mistotebe.net> ---
Maybe you meant something else because I'm not seeing this,
syncprov_matchops->syncprov_qresp already schedules a separate syncprov_qtask
for each active persist session that has anything to send out. Those sessions
each have a separate response queue, sharing a reference to the resinfo
provided.
And those tasks then run independent of each other sending messages (since
ITS#5985 just one message at a time), reclaiming syncres and since ITS#8039
possibly resinfo as they make progress. Also verified all of this at runtime.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6942
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|--- |High
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Fairly critical for 2.7.0 so that we can better handle replicated environments
with chaining where MMR is in play.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9861
Issue ID: 9861
Summary: Read-only databases can't be opened - regression
introduced with da0527ac
Product: LMDB
Version: unspecified
Hardware: aarch64
OS: Mac OS
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: jocke(a)ordo.one
Target Milestone: ---
Created attachment 905
--> https://bugs.openldap.org/attachment.cgi?id=905&action=edit
Reduced simple test to open the environment that fails
The ability to open an environment in read-only mode when the file permissions
is 'read only' for the user is no longer possible after the commit
da0527ac75b811419b7007202799f96b2edb5aef.
It is simply reproduced by creating a database with e.g. mtest.c, then changing
the permissions to read-only, then running another trivial program trying to
open the environment in read-only mode / no-lock mode fails.
Specifically, after some investigation it seems that the check on line 5516 "if
(!(flags & (MDB_RDONLY|MDB_WRITEMAP))) {" was removed in the above commit such
that mdb_fopen() is called (presumably incorrectly?).
Returning that guard check seems to restore functionality, but I'm not familiar
enough with the code base to say that is a valid fix - but seems likely.
I applied that single change here:
https://github.com/hassila/swift-lmdb/tree/hassila-mdb-merge-patch
with this commit:
https://github.com/hassila/swift-lmdb/commit/c940b4c807c278cea43d2e3858dc22…
To reproduce with a clean checkout:
1. make
2. mkdir tested
3. ./mtest
4. chmod -wx testdb/data.mdb
5. run the attached program (reduced from real code base)
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9859
Issue ID: 9859
Summary: fix test
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: hamano(a)osstech.co.jp
Target Milestone: ---
Created attachment 904
--> https://bugs.openldap.org/attachment.cgi?id=904&action=edit
openldap-2.5-fix_test.patch
1. specifiy modulepath and moduleload
moduleload ../rel/mod.la works on build directry ex: make test
but it doesn't work with installed slapd.
It should be specified the modulepath and moduleload separately like other
tests.
```
modulepath ../servers/slapd/overlays/
moduleload mod.la
```
2. skip test020-proxycache for back-wt
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9799
Issue ID: 9799
Summary: Clearing pending ops on Bind
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
When slapd receives some operations before it has started processing a queued
bind, those get added into conn->c_ops_pending and c_n_pending_ops is updated
accordingly.
Bind then eventually invokes connection_abandon() which forgets to zero out
c_n_pending_ops and the connection remains unusable forever.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6461
Ondřej Kuzník <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.5.0 |2.5.12
Group|OpenLDAP-devs |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9157
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
head:
• 2c0707cf
by Howard Chu
ITS#9157: check for NULL ld
RE26 (2.6.3):
• 6675535c
by Howard Chu at 2022-06-03T20:29:24+00:00
ITS#9157: check for NULL ld
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9020
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
head:
• 737bcd7f
by Ondřej Kuzník at 2022-06-03T16:52:37+00:00
ITS#9020 Reinstate olcAutomaticGroups and document its deprecation
RE26 (2.6.3):
• 4a755258
by Ondřej Kuzník at 2022-06-03T17:42:35+00:00
ITS#9020 Reinstate olcAutomaticGroups and document its deprecation
RE25 (2.5.13):
• 02ddd515
by Ondřej Kuzník at 2022-06-03T17:43:55+00:00
ITS#9020 Reinstate olcAutomaticGroups and document its deprecation
--
You are receiving this mail because:
You are on the CC list for the issue.