According to the issue report, the connection 0's DN appears not only
once, but twice, in some circumstances. Duplicated DN should not have
appeared in server response.
Apart from that, connection 0 does not serve any purpose for LDAP
clients, therefore its connection details are not useful.
What do you think?
On 10/04/15 14:29, Michael Ströder wrote:
> The patch is a proposed resolution to the issue.
> To prevent monitor backend from returning invalid result about
> Connection 0, it will simply not report information about the
> connection 0.
Indeed I do understand what your patch does.
But what is the real problem with Connection 0 you're trying to solve?
Note that slapd internally access the database(s). So your monitoring
checks should simply ignore this Connection 0.