Marco Pizzoli wrote:

Hi Howard, thanks for this work.

I noticed that you give me a baseDN under which I can have operations logged. If I would like to exclude one subtree from my principal tree, I need to specify all the baseDN of other sibling-subtrees. To do this do I need to poli-invoke accesslog overlay?

No, you can specify logbase multiple times in a single overlay.

Possibly we can extend the directive to handle exclusion as well as inclusion, to simplify this case.

Thanks again Marco

On Wed, Feb 23, 2011 at 3:15 AM, Howard Chu <hyc@symas.com mailto:hyc@symas.com> wrote:

marco.pizzoli@gmail.com <mailto:marco.pizzoli@gmail.com> wrote:

    Full_Name: Marco Pizzoli
    Version: ALL
    OS:
    URL: ftp://ftp.openldap.org/incoming/
    Submission from: (NULL) (193.41.84.11)


    Hi,
    this is a feature request.

    I would like to have accesslog writing to his db only ldap operations
    that match
    some sort of filter, or, in particular, to not to log searches that
    matches a
    specific pattern.

    This request is spotted by some ldap clients that I have that every
    30seconds do
    a dummy ldap search only to keep alive their connection to the ldap
    server.
    These searches are frequent and I have many of these clients in my
    deploy, so my
    accesslog become full of not significant entries.


I've added a simple subtree-matching feature to accesslog in HEAD. Please
test and let us know if it addresses this request.

--
  -- Howard Chu
  CTO, Symas Corp. http://www.symas.com
  Director, Highland Sun http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP http://www.openldap.org/project/

-- _________________________________________ Non è forte chi non cade, ma chi cadendo ha la forza di rialzarsi. Jim Morrison