<quote who="Aaron Richton">
In the spirit of starting with the obvious, do you find auditContext under cn=Subschema?
I'll check ;-)
But why would this attribute get into the normal data dir?
On Mon, 3 Dec 2007, Gavin Henry wrote:
Hi All,
I blitzed my consumer to test something, and now I'm seeing in its logs:
syncrepl_message_to_entry: rid=000 mods check (auditContext: attribute type undefined)
I don't have an accesslog on the consumer, only auditlog for testing so I can document it.
Any ideas?
Gavin.
-- Kind Regards,
Gavin Henry. Managing Director.
T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry@suretecsystems.com
Open Source. Open Solutions(tm).
Gavin Henry wrote:
<quote who="Aaron Richton"> > In the spirit of starting with the obvious, do you find auditContext under > cn=Subschema?
I'll check ;-)
But why would this attribute get into the normal data dir?
that attribute is added to the producer to provide a pointer to the database that contains the log. The attributeType itself is defined by slapo-accesslog(5), so the overlay should be present (but does not need to be instantiated; just compiled in or, if built as module, loaded) in the consumer in order to have that attribute defined.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati@sys-net.it ---------------------------------------
openldap-software@openldap.org
-
Gavin Henry -
Pierangelo Masarati