https://bugs.openldap.org/show_bug.cgi?id=6138
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.5.1 |2.6.0
Keywords|OL_2_5_REQ |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7748
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|replication |
Resolution|--- |WONTFIX
Status|UNCONFIRMED |RESOLVED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=5973
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
Keywords|replication |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6097
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|OL_2_5_REQ |
Target Milestone|2.5.1 |2.6.0
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8307
--- Comment #10 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
trunk:
commit eefe12366c5c6de25a9a7067000b443d76043725
Author: Howard Chu <hyc(a)openldap.org>
Date: Wed Jan 13 16:35:43 2021 +0000
ITS#8307 fix slapo-accesslog: noop if logDB isn't open yet
Add be_flag for DB OPEN status
commit 85b68aa5e221397081249fe5efe7330a6d738ecf
Author: Howard Chu <hyc(a)openldap.org>
Date: Wed Jan 13 16:39:24 2021 +0000
ITS#8307 slapo-dds: mark internal searches as do_not_cache
commit 9d440e3d2829258b803a2e663343c05341945446
Author: Howard Chu <hyc(a)openldap.org>
Date: Wed Jan 13 16:58:42 2021 +0000
ITS#8307 slapo-accesslog additional check
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8689
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Target Milestone|2.5.1 |---
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8950
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8950
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
Keywords|OL_2_5_REQ, replication |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8950
--- Comment #2 from Howard Chu <hyc(a)openldap.org> ---
Unable to reproduce in current master.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8950
--- Comment #1 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Ondřej Kuzník from comment #0)
> Full_Name: Ondrej Kuznik
> Version: master
> OS: Linux
> URL:
> Submission from: (NULL) (82.10.24.68)
>
>
> Trying to reproduce a potential lockup between TXN support and accesslog, I
> have
> instead come across a segfault in TXN handling.
>
> With the following config:
>
> database mdb
> suffix cn=log
> directory ./log
>
> database mdb
> suffix cn=test
> directory ./db
>
> overlay accesslog
> logdb cn=log
> logops writes
>
> Make sure cn=test entry exists and issue ldapmodify -E '!txn=commit' with
> dn: cn=test
> changetype: modify
>
> slapd segfaults with the following picked up by valgrind:
> I doesn't seem to happen without accesslog configured.
What is the expected behavior, for both the mainDB op and the logDB op
to occur within a single transaction? That is not possible at the moment
since transactions are only valid within a single database.
--
You are receiving this mail because:
You are on the CC list for the issue.