https://bugs.openldap.org/show_bug.cgi?id=6740
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6567
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|TEST |FIXED
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=6509
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|TEST |FIXED
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=6475
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6467
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6306
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|TEST |FIXED
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=6300
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6269
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6194
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|TEST |FIXED
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=6165
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6136
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6035
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|TEST |FIXED
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=5573
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=5540
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=5422
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9277
Issue ID: 9277
Summary: restart 3+ providers at once burns CPU forever
Product: OpenLDAP
Version: 2.4.50
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: michael(a)stroeder.com
Target Milestone: ---
I have tiny VMs configured as Æ-DIR servers, 5 providers (multi-provider
replication) and 5 read-only consumers each syncing with all providers.
Restarting all consumers at once simply works, no matter how many of the
providers are up.
Restarting only two providers at once also works.
But when restarting more than two providers at once all of thems seem to hang
eating up CPU.
It could be the same issue like ITS#8650 / ITS#9210 but those only mention
GNUTLS being affected. But all my Æ-DIR test servers run slapd built against
OpenSSL (openSUSE, Debian buster, CentOS7).
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9015
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.4.54
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9353
Issue ID: 9353
Summary: back-monitor confuses frontendDB with suffix ""
databases
Product: OpenLDAP
Version: 2.4.53
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
If a database is configured with zero length suffix, supplemental monitoring
entries/attributes that are to be registered against that database show up on
the cn=FrontendDB,cn=Databases,cn=Monitor entry instead.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9359
Issue ID: 9359
Summary: syncrepl_op_modify can create invalid mods
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: replication
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
In Delta MPR, if a modify gets delayed in reaching another server and another
(later) modify has already changed that entry, its parts are checked by
syncrepl_op_modify.
Replaces will then be split into a delete+add pairs so they can be resolved
separately, but a bug in mods_dup happily creates an (illegal) empty add if the
replace didn't contain any values.
Fix coming.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9355
Issue ID: 9355
Summary: Delta-sync MPR can fail to recreate entries
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
If an entry is missing on one host and a mod for that DN comes in from another,
it should attempt a fallback to retrieve the latest version.
That does not seem to happen in all cases. At least syncrepl_op_modify does not
seem to propagate the error from overlay_entry_get_ov correctly, instead it
ignores the mod and absorbs the CSN.
https://git.openldap.org/openldap/openldap/-/merge_requests/176
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9345
Issue ID: 9345
Summary: Restarted consumer with syncprov may have empty cookie
Product: OpenLDAP
Version: 2.4.52
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
On a relatively fresh node with both syncrepl and syncprov, after some writes
have occurred, if the consumer config is deleted and re-added, it's possible
the consumer won't see the current cookie. On startup it checks the local
database for contextCSN, but if syncprov has been caching cookie updates it may
not have been written to the DB yet. (And on an older server, the contextCSN
may be present in the DB, but stale relative to the state syncprov has cached.)
The consumer calls check_syncprov on subsequent iterations, but it ought to
also call it on startup, just in case.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8102
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=9352
Issue ID: 9352
Summary: delta-sync SEGV modifying zero-length context entry
Product: OpenLDAP
Version: 2.4.53
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
With a zero-length suffix, the context entry is usually a glue entry. It gets
created without an entryCSN. If an incoming mod updates it, syncrepl will crash
trying to find its entryCSN.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9330
Issue ID: 9330
Summary: Need to fully serialize delta-syncrepl
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
While using delta-syncrepl was supposed to fully serialize updates due to the
use of the accesslog DB, in extremely high write driven environments it became
clear this wasn't entirely the case. This would cause systems to constantly go
into mini REFRESH states as changes came in out of order.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9342
Issue ID: 9342
Summary: delta-sync: relax requirements on delete ops
Product: OpenLDAP
Version: 2.4.52
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
Currently if the delta-sync consumer encounters any unexpected changes it
always falls back to a regular refresh. We should allow it to proceed when a
Delete op fails with NoSuchObject. While unexpected changes are still an
indication of inconsistent logs, we can still safely advance to the next op in
the sequence before giving up (if necessary) since the outcome is the same.
The plain syncrepl consumer already has the same behavior for delete ops.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9361
Issue ID: 9361
Summary: accesslog logpurge generates new CSNs for its deletes
Product: OpenLDAP
Version: 2.4.53
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
The delete operations that are performed by logpurge are for internal
bookkeeping purposes and should not have new CSNs attached to them. In
the current code, since each delete has a new valid CSN, the logDB's
contextCSN becomes newer than its main DB's, and this can trigger the
syncprov on the logDB to send NEW_COOKIE messages to all delta consumers.
Meanwhile, the mainDB's contextCSN hasn't changed. As a result, the
consumers' contextCSN for that SID will be newer than the provider's.
Fix coming shortly.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9331
Issue ID: 9331
Summary: New Mirror in NL
Product: website
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: website
Assignee: bugs(a)openldap.org
Reporter: info(a)lyrahosting.com
Target Milestone: ---
Hi,
With much pleasure, Lyra Hosting has created a new Mirror for OpenLDAP.
Mirror is located in Netherland
access methods: http and https
Your mirror's available bandwidth: 200mbps
An administrative contact email: admin(a)lyrahosting.com
http://mirror.lyrahosting.com/OpenLDAP/https://mirror.lyrahosting.com/OpenLDAP/
Kindly regards
Dennis
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9017
--- Comment #23 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• d1814f7e
by Howard Chu at 2020-10-11T01:45:45+01:00
ITS#9017 fixes for encryption
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8618
--- Comment #22 from Konstantin Andreev <grapvar(a)gmail.com> ---
(In reply to Howard Chu from comment #21)
>
> It's quite poor etiquette to respond to a thread without reading it from the
> beginning. This ticket already makes the advantage clear.
I certainly read the thread before responding. But I admit I should make this
clear to facilitate the discussion.
The only advantage I could assume from 2018-year thread is the ability to "Not
to fix" the bug originally called [ldapsearch - unexpected behavior with "-h
URI -p PORT"].
If this is what you mean as "advantage" then I could say that even simple
WONTFIX would be better, because it, at least, does not harm current ldaptools
users.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8618
--- Comment #21 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Konstantin Andreev from comment #20)
> The most balanced approach is to remove *being used* features only when they
> come into conflict with new features or enhancements. Not just because
> "there is another way". What is the advantage in removing -h/-p?
It's quite poor etiquette to respond to a thread without reading it from the
beginning. This ticket already makes the advantage clear.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8618
--- Comment #20 from Konstantin Andreev <grapvar(a)gmail.com> ---
(In reply to Howard Chu from comment #19)
> >
> > I think you might be mistaken with removing -h/-p. Why not to leave it
> > as-is? It just works.
>
> These options have been deprecated since 2000, so you've had literally 20
> years to migrate away from them. "It just works" is incorrect, these options
> are inadequate for most modern use cases. E.g., they're insufficient for
> specifying ldaps or ldapi connections, while using -H with a URI handles all
> use cases.
You should ask instead: how many people do use them? It costs negligible to
zero for you to just leave these features well enough alone, but it always
costs money and efforts to migrate away.
> These options have been deprecated since 2000, so you've had literally 20
> years to migrate away from them.
If you are locked in OpenLDAP. But people use them because they are "lowest
common denominator", supported by virtually any ldaptools suite. If you discard
these options, you become (very?) special.
The most balanced approach is to remove *being used* features only when they
come into conflict with new features or enhancements. Not just because "there
is another way". What is the advantage in removing -h/-p?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8618
--- Comment #19 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Konstantin Andreev from comment #18)
> A lot of admin people will now be forces to rewrite, test and debug their
> hard-worked and stable management/startup/monitoring scripts. Multiply this
> by N, because unforeseen corner cases always arise with time.
>
> Some times such changes must be conducted via external
> auditing/certification authority, that is a way costlier.
>
> And last, but not least, ... [-h] and [-p] are de-facto standard for
> ldap-tools.
>
> E.g., at the moment I use identical ldapsearch command line parameters on
> Linux and on Solaris, but since then I should learn, train and use two
> different ways, with unavoidable confusing from time to time.
>
> I think you might be mistaken with removing -h/-p. Why not to leave it
> as-is? It just works.
These options have been deprecated since 2000, so you've had literally 20 years
to migrate away from them. "It just works" is incorrect, these options are
inadequate for most modern use cases. E.g., they're insufficient for specifying
ldaps or ldapi connections, while using -H with a URI handles all use cases.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8618
--- Comment #18 from Konstantin Andreev <grapvar(a)gmail.com> ---
A lot of admin people will now be forces to rewrite, test and debug their
hard-worked and stable management/startup/monitoring scripts. Multiply this by
N, because unforeseen corner cases always arise with time.
Some times such changes must be conducted via external auditing/certification
authority, that is a way costlier.
And last, but not least, ... [-h] and [-p] are de-facto standard for
ldap-tools.
E.g., at the moment I use identical ldapsearch command line parameters on Linux
and on Solaris, but since then I should learn, train and use two different
ways, with unavoidable confusing from time to time.
I think you might be mistaken with removing -h/-p. Why not to leave it as-is?
It just works.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8618
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|ldapsearch - unexpected |Remove deprecated -h HOST
|behavior with "-h URI -p |and -p PORT options from
|PORT" |clients
Resolution|--- |TEST
Status|UNCONFIRMED |RESOLVED
--- Comment #17 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 66af4cfd
by Quanah Gibson-Mount at 2020-10-01T21:27:59+00:00
ITS#8618 - Remove deprecated -h and -p options to client tools
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8872
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|IN_PROGRESS |RESOLVED
Keywords|OL_2_5_REQ |
--- Comment #4 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 2dace701
by Quanah Gibson-Mount at 2020-10-01T16:41:34+00:00
ITS#8872 - Rename configure.in to configure.ac
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8872
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |IN_PROGRESS
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
https://git.openldap.org/openldap/openldap/-/merge_requests/187
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8872
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
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=8872
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|1 |0
Resolution|FIXED |---
Target Milestone|--- |2.5.0
Status|VERIFIED |UNCONFIRMED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8486
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.4.54
--- Comment #12 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE24:
commit 234230f286f8d67c4d4bf590accbd483172dbdf8
Author: Ondřej Kuzník <ondra(a)openldap.org>
Date: Thu Oct 26 12:00:20 2017 +0100
ITS#8486 Switch sessionlog to use TAVL
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=5422
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |TEST
Keywords|OL_2_6_REQ |
Target Milestone|2.6.0 |2.5.0
--- Comment #2 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
• 3f5293e1
by Ondřej Kuzník at 2020-09-24T23:34:36+00:00
ITS#5422 Save errno before passing it to Debug()
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8486
--- Comment #11 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Note: OpenLDAP 2.5 has further work converting the sessionlog to a btree:
Commits:
• d2036cec
by Ondřej Kuzník at 2020-09-25T00:07:50+00:00
ITS#8486 Switch sessionlog to use TAVL
• 8f8774c0
by Howard Chu at 2020-09-25T00:07:50+00:00
ITS#8486 Minor play_sessionlog cleanup
Fix logmsg uuidstr.
Shortcut finding start of playback.
Allow dup CSNs in log, but with different UUIDs. All
non-present deletes in a refresh use the same CSN.
• 98d5c5c6
by Ondřej Kuzník at 2020-09-25T00:07:50+00:00
ITS#8486 Protect tavl_* calls in play_sessionlog
• 1915cb96
by Howard Chu at 2020-09-25T00:07:50+00:00
ITS#8486 use kbtree for sessionlog
Saves about 20% CPU time and RAM
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8636
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|UNCONFIRMED |RESOLVED
Keywords|OL_2_5_REQ |
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• f3e86d3d
by Quanah Gibson-Mount at 2020-09-25T04:29:59+00:00
ITS#8636 - Fix DESC for deltaCRL attribute
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8341
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• fe3636df
by Quanah Gibson-Mount at 2020-09-25T02:05:55+00:00
ITS#8341 - Add matching rule to the namingContexts attr
--
You are receiving this mail because:
You are on the CC list for the issue.
If you are looking for the best cheapest SEO service company for the search engine optimization and digital marketing of your business website then BEST SEO is the right option for you, We provide the cheapest digital marketing services in Pakistan and Internationally as well.
The services we offer are:
• Search Engine Optimization Services
• Social Media Marketing Services
• Content Writing Services
• Article Writing Services
• Press Release Writing Services
• PPC Services
• Blog Writing Services
To hire my services, visit my business website https://bestseo.com.pk
https://bugs.openldap.org/show_bug.cgi?id=7161
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=9293
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9045
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |replication
Severity|normal |blocker
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8102
--- Comment #9 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE24:
Commits:
• 584858eb
by Howard Chu at 2020-09-22T21:37:09+00:00
ITS#8102 syncrepl: only use trylock on the cn=config DB
--
You are receiving this mail because:
You are on the CC list for the issue.