On 17 January 2011 07:44, wrote:
> Can anyone give me any clues as to why this might happen? Is there a
>> quit command (I'm already exiting on "QUIT" or empty line from stdin)
>> that the pipe backend sends? Or maybe this is a bug?
>>
>
> I found this in our perl pipe backend:
>
> LINE: while( <
Can anyone give me any clues as to why this might happen? Is there a
quit command (I'm already exiting on "QUIT" or empty line from stdin)
that the pipe backend sends? Or maybe this is a bug?
I found this in our perl pipe backend:
LINE: while( <> ) {
exit if getppid() == 1; #Exit, cause my p
Hi there,
I've written a custom backend which I'm using with the Pipe backend. It
works perfectly, accepts queries and answers correctly, etc, however for
some reason the processes don't exit cleanly when the server is
stopped/restarted.
For example when I try and stop the server, the init.d scri
Hi Norbert,
We would really appreciate any info you might be able to provide
regarding upgrading plans for the LDAP backend, esp. considering there
is an upcoming 3.0 release.
For example, besides DNSSec support (see below), I am aware of issues
313 (associated with 317), 318 (on which a dis
Thanks Norbert,
Although the OpenLDAP guys would not encourage such a change (and,
formally speaking, they are right), since the aRecord attribute
definition (in the standard distribution cosine.schema file) is
according to RFC 1274 without a SUBSTR matching rule, I guess it's the
easiest sol
