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

Re: database monitor

To: "Friedrich Locke" <friedrich.locke@gmail.com>
Subject: Re: database monitor
From: masarati@aero.polimi.it
Date: Wed, 6 Jul 2011 01:17:43 +0200 (CEST)
Cc: openldap-technical@openldap.org
Importance: Normal
In-reply-to: <CANMDHqcFbwV2p8-1OyV0cfnKRJUvyqRGAWv6zu9W2aiyOny1mQ@mail.gmail.com>
References: <CANMDHqcrAOZD-55PFcHvpDxpbcKZ9QCXXccivnQzzdW7uKL9Sw@mail.gmail.com> <fc85b1aa16ac46cba450c9cc9bbfa1f9.squirrel@www.aero.polimi.it> <CANMDHqcUSp0wuXqCQZRP8c8AS9nM2aQmhxxaV2JWOE4hkCPWnw@mail.gmail.com> <CANMDHqcFbwV2p8-1OyV0cfnKRJUvyqRGAWv6zu9W2aiyOny1mQ@mail.gmail.com>
User-agent: SquirrelMail/1.4.15

> Backend ACL: access to *
>         by * none
>
> config_back_db_open: line 0: warning: cannot assess the validity of
> the ACL scope within backend naming context

Read carefully: it's back-config that implicitly instantiates that rule,
so it has nothing to do with back-monitor.  Moreover, the message only
pops up when you enable ACL logging, which is only useful for debugging. 
Only enable it when needed, and the message will disappear.

p.

References:
- database monitor
  - From: Friedrich Locke <friedrich.locke@gmail.com>
- Re: database monitor
  - From: masarati@aero.polimi.it
- Re: database monitor
  - From: Friedrich Locke <friedrich.locke@gmail.com>
- Re: database monitor
  - From: Friedrich Locke <friedrich.locke@gmail.com>

Prev by Date: Re: database monitor
Next by Date: Re: database monitor
Index(es):
- Chronological
- Thread