Edward Z. Yang wrote:
Excerpts from Howard Chu's message of Mon Oct 18 15:23:02 -0400 2010:
The function would return a zero-length berval in that case. There's a
difference between no values, and one value of zero length.
Sure, but for the programmer, there is definitely a difference between
KALINOWSKI, Piotr (Piotr) wrote:
> I am trying to build OpenLDAP version 2.2.17 with the gdbm
back end.
>>
>> You should not use OpenLDAP 2.2.x (set to historic years ago)
>> and you should definitely not use gdbm-based backend. You
>> won't get any help on the mailing lists.
>
> Thanks f
Excerpts from Howard Chu's message of Mon Oct 18 15:23:02 -0400 2010:
> The function would return a zero-length berval in that case. There's a
> difference between no values, and one value of zero length.
Sure, but for the programmer, there is definitely a difference between
p == NULL and *p == N
Emmanuel Lecharny wrote:
On 10/18/10 12:48 PM, Howard Chu wrote:
But it's certainly stupid for the server to attach the attribute to
the response with no values, since this is obviously NOT an attrsOnly
search response.
What about an AttributeType with an OctetString syntax ? It may have an
> -Original Message-
> From: Michael Ströder [mailto:mich...@stroeder.com]
> Sent: Monday, October 18, 2010 5:52 PM
> >>> I am trying to build OpenLDAP version 2.2.17 with the gdbm
> >> back end.
>
> You should not use OpenLDAP 2.2.x (set to historic years ago)
> and you should definitel
> -Original Message-
> From: Aaron Richton [mailto:rich...@nbcs.rutgers.edu]
> Sent: Monday, October 18, 2010 5:03 PM
>
> You are setting yourself for immense pain; the gdbm backend
> in that version will almost certainly suffer from (possibly
> irreparable) corruption. The only valid re
KALINOWSKI, Piotr (Piotr) wrote:
>>> I am trying to build OpenLDAP version 2.2.17 with the gdbm
>> back end.
You should not use OpenLDAP 2.2.x (set to historic years ago) and you should
definitely not use gdbm-based backend. You won't get any help on the mailing
lists.
Ciao, Michael.
On 10/18/10 12:48 PM, Howard Chu wrote:
But it's certainly stupid for the server to attach the attribute to
the response with no values, since this is obviously NOT an attrsOnly
search response.
What about an AttributeType with an OctetString syntax ? It may have an
empty value...
--
Regar
On Mon, 18 Oct 2010, KALINOWSKI, Piotr (Piotr) wrote:
Hello,
I am trying to build OpenLDAP version 2.2.17 with the gdbm back end. The
platform is Solaris 10 on SPARC. However, the configure script fails with the
following error:
./configure --enable-ldbm --with-ldbm-api=gdbm --enable-shell
Hello Howard,
Thank you for your analysis. In this case, I suggest that a note that
a NULL may be returned by OpenLDAP by ldap_get_values and ldap_get_values_len,
so that programmers are advised they need to special case this non-error
condition.
--- ldap_get_values.3 2010-04-13 21:22:39.0
Benjamin,
You are probably right, but it is not my decision. Btw, does the current
version (2.4) support GDBM? I did not find it in configure script. If the
support was removed, updating OpenLDAP would need the migration of databases,
too...
Piotr
> -Original Message-
> From: Benja
Update: the serverSort thing was a false-positive this morning, I
guess the client was still caching.
...
Oct 18 15:52:23 examplehost slapd[24946]: conn=9373 op=168 SEARCH
RESULT tag=101 err=18 nentries=0 text=serverSort control: No ordering
rule
Oct 18 15:52:23 examplehost slapd[24946]: conn=9373
Hello Piotr,
you should consider updating your ancient OpenLDAP-Server. :)
Bye, Benjamin.
On Mon, Oct 18, 2010 at 14:14, KALINOWSKI, Piotr (Piotr)
wrote:
> Hello,
>
> I am trying to build OpenLDAP version 2.2.17 with the gdbm back end. The
> platform is Solaris 10 on SPARC. However, the configur
On Friday 15 October 2010 20:45:11 Ryan Steele wrote:
> For reference, this is a slightly older installation (2.4.17 on
> Ubuntu). I was recently informed that we had to implement the
> ppolicy overlay ASAP for compliance reasons in this environment. I
> don't have time to upgrade this particular
Hello,
I am trying to build OpenLDAP version 2.2.17 with the gdbm back end. The
platform is Solaris 10 on SPARC. However, the configure script fails with the
following error:
./configure --enable-ldbm --with-ldbm-api=gdbm --enable-shell --enable-crypt
--disable-bdb
...
checking for GDBM librar
Edward Z. Yang wrote:
Hello all,
I was mucking around with OpenLDAP and noticed that ldap_get_values_len
was returning NULL without setting a corresponding error code. Intruiged
by this behavior, I did some debugging, and found that it was doing so
on nsslapd-referral as generated by a Fedora 1
Hello all,
I was mucking around with OpenLDAP and noticed that ldap_get_values_len
was returning NULL without setting a corresponding error code. Intruiged
by this behavior, I did some debugging, and found that it was doing so
on nsslapd-referral as generated by a Fedora 1.2.5 or 1.2.6 directory
For reference, this is a slightly older installation (2.4.17 on Ubuntu). I was
recently informed that we had to
implement the ppolicy overlay ASAP for compliance reasons in this environment.
I don't have time to upgrade this
particular cluster at the moment, so I'm trying to work with what I've
Hi diego,
thanks for you advise. I created two new Overlays as you said and
tried to set the attribute-set that I googled from some other guys.
These are probably wrong. Finally, that solved the messages that
appeared in the slapd log, but didn't solve the problem on the solaris
hosts.
Too bad. :/
Dear folks:
If any one has the syntax for adding proxy addresses in the LDIF file along
with the normal mail attribute that will be really appreciated if you can share
the Syntax or the link and also the modifications to schema files with the
details.
Cheers!!
Ram
Req:
20 matches
Mail list logo
