From marco.pizzoli@gmail.com Tue Feb 1 15:34:03 2011 From: marco.pizzoli@gmail.com To: openldap-bugs@openldap.org Subject: Re: ITS#6815 Date: Tue, 01 Feb 2011 15:34:03 +0000 Message-ID: <201102011534.p11FY38P026748@boole.openldap.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5636876080614406018==" --===============5636876080614406018== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable --001636e0a68c56af9b049b3a400d Content-Type: text/plain; charset=3DISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, yes but not all my clients are so flexible. A helpful usage, in my deploy, would be in populating a database with only BIND operations. By now this is not possible. Thanks Marco Pizzoli On Sun, Jan 30, 2011 at 9:12 PM, wrote: > > 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. > > For this specific purpose, your clients could perform an operation that i=3D s > not logged; for example, search the rootDSE. > > p. > > --=3D20 _________________________________________ Non =3DE8 forte chi non cade, ma chi cadendo ha la forza di rialzarsi. Jim Morrison --001636e0a68c56af9b049b3a400d Content-Type: text/html; charset=3DISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,
yes but not all my clients are so flexible.

A helpful usage,=3D in my deploy, would be in populating a database with only BIND operations.=3D By now this is not possible.

Thanks
=3DA0=3DA0=3DA0=3DA0=3DA0 Marc= o Pizzol=3D i

On Sun, Jan 30, 2011 at 9:12 PM, <masarati(a)aero.polimi= .it<=3D /a>> wrote:
> 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.

For this specific purpose, your clients could perform an operation that is<=3D br> not logged; for example, search the rootDSE.

p.




--
_______________________= =3D __________________
Non =3DE8 forte chi non cade, ma chi cadendo ha la forz= =3D a di rialzarsi.
=3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =3DA= 0 Jim Morrison
--001636e0a68c56af9b049b3a400d-- --===============5636876080614406018==--