From marco.pizzoli@gmail.com Thu Jul 15 10:25:30 2010 From: marco.pizzoli@gmail.com To: openldap-bugs@openldap.org Subject: ITS#6576 Date: Thu, 15 Jul 2010 10:25:29 +0000 Message-ID: <201007151025.o6FAPTI2038049@boole.openldap.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8186894662541835693==" --===============8186894662541835693== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit --0016e6de0432b2d346048b6a8223 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I see only now that my ITS is in closed state, with the note about the use of grep. My initial request is motivated by a heavy trafficated deployment in which access log files are rotated every 3h and the information about the binddn/ip_src fall often in the rotated file. Worst of this, IBM Unix AIX systems permit LDAP integration using a daemon (secldapclntd) which creates a *permanent* pool of connections againts all ldap servers configured. IBM DB2 v9.5+ permit a native ldap integration and the behaviour is analogous to the AIX one. So, if I need to extract specific information about a binddn/ip I have to follow many files and correlate many informations (conn=3D) For my purposes it would be sufficient an extension to slapo-accesslog permitting me to define a filter on the binddn of the activity. Thanks Marco --=20 _________________________________________ Non =E8 forte chi non cade, ma chi cadendo ha la forza di rialzarsi. Jim Morrison --0016e6de0432b2d346048b6a8223 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I see only now that my ITS is in closed state, with the note about the use = of grep.

My initial request is motivated by a heavy trafficated depl= oyment in which access log files are rotated every 3h and the information a= bout the binddn/ip_src fall often in the rotated file.

Worst of this, IBM Unix AIX systems permit LDAP integration using a dae= mon (secldapclntd) which creates a *permanent* pool of connections againts = all ldap servers configured.
IBM DB2 v9.5+ permit a native ldap integrat= ion and the behaviour is analogous to the AIX one.

So, if I need to extract specific information about a binddn/ip I have = to follow many files and correlate many informations (conn=3D<number>= )

For my purposes it would be sufficient an extension to slapo-acces= slog permitting me to define a filter on the binddn of the activity.

Thanks
=A0=A0=A0 Marco



--
_________= ________________________________
Non =E8 forte chi non cade, ma chi cade= ndo ha la forza di rialzarsi.
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ji= m Morrison
--0016e6de0432b2d346048b6a8223-- --===============8186894662541835693==--