[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#7280) accesslog write to subentry of log database

This is a multi-part message in MIME format.
--------------060900070300040405040602
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sent: Sun May 27 2012 19:02:08 GMT-0400 (EDT)
From: Howard Chu <hyc@symas.com>
To: openldap@stormcloud9.net openldap-its@openldap.org
Subject: Re: (ITS#7280) accesslog write to subentry of log database
> openldap@stormcloud9.net wrote:
>> Full_Name: Patrick Hemmer
>> Version: 2.4.31
>> OS: Linux RHEL6
>> URL:
>> Submission from: (NULL) (98.211.220.204)
>>
>>
>> This is a feature request (mostly).
>>
>> Currently the accesslog overlay is only capable of writing to the 
>> base DN of a
>> log database, and not a subentry of that database. Specifying the DN 
>> to a
>> specific subentry for the "logdb" parameter ends up writing to the 
>> base DN of
>> the database instead.
>>
>> The main reason for this is so that multiple accesslog overlays can 
>> write to the
>> same backend database, and not have to create a separate database for 
>> each
>> overlay. Currently if you try to give multiple accesslog overlays the 
>> same
>> database, it causes deadlock issues (or it appears to be a deadlock) 
>> and write
>> operations end up hanging. I'm not sure if this should be considered 
>> a bug, or
>> just noted as "don't try and do that".
>
> Don't do that. Closing this ITS.
>

This is nonconstructive. I know not to do that, I'm the one who filed 
the ITS...
You don't address the feature request at all, only that it currently 
doesn't work which is why the request was filed in the first place. Is 
logging multiple accesslog overlays to the same backend database unfeasible?

-Patrick

--------------060900070300040405040602
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000066">
    <font color="#000000">Sent: Sun May 27 2012 19:02:08 GMT-0400 (EDT)<br>
      From: Howard Chu <a class="moz-txt-link-rfc2396E" href="mailto:hyc@symas.com";>&lt;hyc@symas.com&gt;</a><br>
      To: <a class="moz-txt-link-abbreviated" href="mailto:openldap@stormcloud9.net";>openldap@stormcloud9.net</a> <a class="moz-txt-link-abbreviated" href="mailto:openldap-its@openldap.org";>openldap-its@openldap.org</a><br>
      Subject: Re: (ITS#7280) accesslog write to subentry of log
      database</font>
    <blockquote cite="mid:4FC2B270.9090900@symas.com" type="cite"><font
        color="#000000"><a class="moz-txt-link-abbreviated" href="mailto:openldap@stormcloud9.net";>openldap@stormcloud9.net</a> wrote:
        <br>
      </font>
      <blockquote type="cite"><font color="#000000">Full_Name: Patrick
          Hemmer
          <br>
          Version: 2.4.31
          <br>
          OS: Linux RHEL6
          <br>
          URL:
          <br>
          Submission from: (NULL) (98.211.220.204)
          <br>
          <br>
          <br>
          This is a feature request (mostly).
        </font>
        <font color="#000000"><br>
          <br>
          Currently the accesslog overlay is only capable of writing to
          the base DN of a
        </font>
        <font color="#000000"><br>
          log database, and not a subentry of that database. Specifying
          the DN to a
          <br>
          specific subentry for the "logdb" parameter ends up writing to
          the base DN of
          <br>
          the database instead.
          <br>
          <br>
          The main reason for this is so that multiple accesslog
          overlays can write to the
        </font>
        <font color="#000000"><br>
          same backend database, and not have to create a separate
          database for each
          <br>
          overlay. Currently if you try to give multiple accesslog
          overlays the same
          <br>
          database, it causes deadlock issues (or it appears to be a
          deadlock) and write
          <br>
          operations end up hanging. I'm not sure if this should be
          considered a bug, or
          <br>
          just noted as "don't try and do that".
          <br>
        </font></blockquote>
      <font color="#000000"><br>
        Don't do that. Closing this ITS.
        <br>
        <br>
      </font>
    </blockquote>
    <font color="#000000"><br>
      This is nonconstructive. I know not to do that, I'm the one who
      filed the ITS...<br>
      You don't address the feature request at all, only that it
      currently doesn't work which is why the request was filed in the
      first place. Is logging multiple accesslog overlays to the same
      backend database unfeasible?<br>
      <br>
      -Patrick<br>
    </font>
  </body>
</html>

--------------060900070300040405040602--