I just checked and only 126.96.36.199-1.el5 is in the epel-testing repo
On Mar 27, 2012, at 9:50, Michael R. Gettes wrote:
I judge from your questions this is not a known problem.
On Mar 27, 2012, at 9:17, Rich Megginson wrote:
> On 03/26/2012 08:25 PM, Michael R. Gettes wrote:
>> I am a little perplexed.
>> I am making a change to a groupOfNames object having some 16069 member
attributes. I am deleting nearly 16000 members and then adding nearly 16000 members. CPU
goes to 100% and never comes down. I have plenty of memory allocated (700MB) to nss-slapd
and I have made the adjustments to allow for large objects (maxbersize). I end up having
to kill -9 slapd. the annoying thing is some times it works, some times it doesn't.
I can't seem to find any common conditions of the failures (or successes).
> Are you using replication? If so, do you see the high CPU usage on the master or on
> Are you able to reproduce with 389-ds-base-188.8.131.52-1 in epel-testing?
>> ds = 184.108.40.206
>> RHEL = 5.7