Received: (qmail 42841 invoked by uid 501); 10 Aug 2000 20:15:40 -0000 Message-Id: <20000810201540.42840.qmail@locus.apache.org> Date: 10 Aug 2000 20:15:40 -0000 From: Glen Barney Reply-To: glen@ldscn.com To: submit@bugz.apache.org Subject: Information on correcting File Descriptor limits in SCO OpenServer 5 X-Send-Pr-Version: 3.110 >Number: 6404 >Category: os-sco >Synopsis: Information on correcting File Descriptor limits in SCO OpenServer 5 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: apache >Arrival-Date: Thu Aug 10 13:20:01 PDT 2000 >Closed-Date: Sun Sep 17 22:33:25 PDT 2000 >Last-Modified: Sun Sep 17 22:33:25 PDT 2000 >Originator: glen@ldscn.com >Release: 1.3.12 >Organization: >Environment: SCO OpenServer 5, all versions, all patches, all compilers >Description: Apache documentation describes the File Descriptor problem, and outlines ways of fixing this problem for certain Operating Systems. SCO OpenServer is not included in this list. The page asks for submissions with information on correcting this problem in other Operating Systems. This report provides the correction for SCO OpenServer. >How-To-Repeat: Configure Apache's httpd.conf file on a server running on SCO so that more than 110 file descriptors are opened. Apache will fail to serve documents under these conditions. >Fix: Edit the /etc/conf/cf.d/stune file or use /etc/conf/cf.d/configure choice 7 (User and Group configuration) and modify the NOFILES kernel parameter to a suitably higher value. SCO recommends a number between 60 and 11000, the default is 110. We raised the limit to 1024 on our server. Relink and reboot, and the new number of descriptors will be available. >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: slive State-Changed-When: Sun Sep 17 22:33:25 PDT 2000 State-Changed-Why: Thanks for the info. >Unformatted: [In order for any reply to be added to the PR database, you need] [to include 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! ]