[Date Prev][Date Next]
Re: both 8 hour 200 vu tests end in a server abort
thanks for that hint. Maybe this is what I missed. Are there any other
to adjust for OpenLDAP apart from the three you mentioned? I didn't
parameters so there are default. For Redhat 3 ES this means:
/proc/sys/kernel/msgmni > 16
/proc/sys/kernel/shmmax > 33554432
/proc/sys/kernel/shmall > 2097152
FYI: For Redhat ES 3 the parameters also stored in /etc/sysctl.conf. To
available immediately type
echo "1024" > /proc/sys/kernel/msgmni
or use sysctl utility.
Quanah Gibson-Mount wrote:
--On Thursday, June 10, 2004 10:36 PM -0700 Trevor Warren
--- Howard Chu <email@example.com> wrote:
You still have neglected to mention what resource
limits are in effect
for the actual slapd process. As such, there is no
evidence that you
have set up your machine correctly. Swearing/cursing
isn't going to
improve the situation.
None of what you have provided in any way shows what resource limits
slapd is running under. Resource limits are defined by the Operating
System. For example, on Debian, I had to modify /etc/sysctl.conf to:
addline /etc/sysctl.conf "kernel.msgmni=1024"
addline /etc/sysctl.conf "kernel.shmmax=3221225472"
addline /etc/sysctl.conf "kernel.shmall=3221225472"
This increases the amount of shared memory available, for example.
Also look at things like ulimit.
Principal Software Developer
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html