os-freebsd/4772: Apache threads give sig 11 when there is reached open files limit on the system

[Domas Mituzas <mi...@dammit.lt>]

>Number:         4772
>Category:       os-freebsd
>Synopsis:       Apache threads give sig 11 when there is reached open files limit on the system
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Jul 26 13:50:01 PDT 1999
>Last-Modified:
>Originator:     midom@dammit.lt
>Organization:
apache
>Release:        1.3.6
>Environment:
FreeBSD mx.nkm.lt 2.2.8-RELEASE FreeBSD 2.2.8-RELEASE #0: 
Mon Nov 30 06:34:08 GMT 1998     
jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC  
i386
>Description:
At first kernel errors about "too many open files" are reported, then apache threads crash (they were crashing and respawning for a rather long period of time).
>How-To-Repeat:
Try a bigger load, so the limit of open files would be reached. Then you will see that 
all threads are dieing and respawning and dieing etc...
>Fix:
the first one - to check for this limit/whatever. and to document, that this can be a serious problem on FreeBSD...
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]