Ah yes, now I remember. It was a chicken and egg problem. It's not a
matter of st->cache_rmm being invalid, it is the fact that
util_ald_alloc() expects to allocate from a util_ald_cache_t*, which is
the reason why we are calling util_ald_create_cache() in the first
place. We have to create one
Hi,
I think my mail wasn't clear :)
All is about the util_ald_alloc function using shm or not, st->cache_rmm
is valid :)
At the beginning, it was util_ald_alloc(unsigned long size) and inside,
when the configure set APR_SHARED_MEMORY, it was using a global rmm_addr.
Then, the patch i did was c
I don't have a problem with this patch, but since NetWare doesn't use
shared memory I am not able to trace down exactly what the issue is.
Can you describe the circumstance where the util_ald_create_cache()
function is called and st->cache_rmm is invalid? By simply looking
through the code, it
Hi,
st->cache_rmm is now invalid because due to non SHM plateform, bnicholes
changed the alloc function util_ald_alloc to receive now
util_ald_cache_t and no more apr_rmm_t.
As we are just before the cache alloc, it's impossible to give
util_ald_alloc a cache object, that's why there, i did a b
Matthieu Estrade wrote:
Here is a little patch, fixing the ldap cache using shared memory.
After the fix for plateform using SHM or not, it was a problem with
cache init, unable to get it's rmm address to alloc memory.
why is st->cache_rmm not filled out (or invalid)?
Hi,
Here is a little patch, fixing the ldap cache using shared memory.
After the fix for plateform using SHM or not, it was a problem with
cache init, unable to get it's rmm address to alloc memory.
I modified the cache alloc for the two cases, with and without SHM, now
not using more util_ald_
