Re: (ITS#4903) dynlist issues with memory allocation

[quanah@stanford.edu]

--On Monday, April 02, 2007 9:42 PM +0200 Pierangelo Masarati 
<ando@sys-net.it> wrote:

> quanah@stanford.edu wrote:
>
>> database        hdb
>> suffix          "dc=stanford,dc=edu"
>> rootdn          "cn=manager,dc=stanford,dc=edu"
>>
>> overlay valsort
>> valsort-attr suOrgContactStanford cn=orgs,dc=stanford,dc=edu weighted
>> valsort-attr suOrgContactWorld cn=orgs,dc=stanford,dc=edu weighted
>>
>> overlay dynlist
>> dynlist-attrset groupOfURLS memberURL member
>>
>> limits group="cn=ldapadmin,cn=applications,dc=stanford,dc=edu"
>> time.soft=unlimited time.hard=unlimited size.soft=unlimited
>> size.hard=unlimited
>
> There it is: "limits" is a database specific directive appearing
> __after__ overlay instantiation.  Try moving all database-specific
> directives __before__ any overlay instantiation.

Ah, I see... So its not just global/db.

So all overlay bits should be listed last?  And I assume this only happens 
when you have more than one overlay in use?  Because it only happens once 
both valsort and dynlist are enabled.


--Quanah


--
Quanah Gibson-Mount
Senior Systems Software Developer
ITS/Shared Application Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html