Howard Chu wrote:
What git commit ID?
As said in former times: Before reporting an ITS I *always* do git pull
checking whether there was something committed after the tested build. If
there was a new commit I always retest.
Ciao, Michael.
Full_Name: Michael Ströder
Version: not relevant
OS: not relevant
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (84.163.25.215)
This is a feature request:
It should be possible to limit effect of ppolicy_forward_updates to certain
events like. Maybe just a list of attributes
--0015174c117a5169be04b1e058e5
Content-Type: text/plain; charset=ISO-8859-1
Quanah,
We have compiled OpenLDAP 2.4.26 with BDB 5.2.36. The OpenLDAP locked up 4
hours into our testing in similar manner to what I have reported earlier. I
believe this issue still occurs on the latest version.
Michael Ströder wrote:
Howard Chu wrote:
What git commit ID?
As said in former times: Before reporting an ITS I *always* do git pull
checking whether there was something committed after the tested build. If
there was a new commit I always retest.
Please just answer the questions. Bear in
h...@symas.com wrote:
Michael Ströder wrote:
Howard Chu wrote:
What git commit ID?
As said in former times: Before reporting an ITS I *always* do git pull
checking whether there was something committed after the tested build. If
there was a new commit I always retest.
Please just answer