You can try increasing the kernel semaphore parameters in /proc. We have to do this for the database that we run. We put the following line in /etc/rc.d/rc.local to increase the params on each reboot:
# Set the semaphore kernel params (now in /proc) /bin/echo "250 32767 32 256" > /proc/sys/kernel/sem This setting only works with 2.4.x kernels. If you have a 2.2.x kernel you will have to edit some kernel files and recompile your kernel. I believe the file to edit is /usr/src/linux/include/linux/sem.h. I don't have a 2.2 kernel source tree to look at so I don't remember the actual parameters to modify in that file, but take a look at it if you have a 2.2 kernel. Hope this helps, Andy. -----Original Message----- From: Tomás García Ferrari [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 10:12 AM To: RedHat List Subject: Problem with semaphores Hello, My server is day after day increasing the used semaphore arrays. My first idea was that the daily apache restart (using /etc/rc.d/init.d/httpd restart) was causing this: there were a lot of apache owned semaphore arrays. I switched the restart command (to /usr/sbin/apachectl graceful) and this helped a bit. The semaphore arrays don't increase so fast. But nevertheless, they increase and at some point, they reach the 128 limit (and then Apache won't start anymore...) My problems are: a. Most of the semaphore arrays are owned by root... How do I know which ones can I safely delete? b. How to avoid this increasing semaphore arrays problem..? I will appreciate any help. Regards, Tomás +-- --+ Tomás García Ferrari Bigital http://bigital.com/ +-- --+ -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
