Received: (qmail 17603 invoked by uid 2012); 26 Apr 1998 12:26:15 -0000 Message-Id: <19980426122615.17602.qmail@hyperreal.org> Date: 26 Apr 1998 12:26:15 -0000 From: Tom Mornini Reply-To: tmornini@infomania.com To: apbugs@hyperreal.org Subject: mod_status always displays 256 possible connection slots X-Send-Pr-Version: 3.2 >Number: 2138 >Category: mod_status >Synopsis: mod_status always displays 256 possible connection slots >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: suspended >Class: change-request >Submitter-Id: apache >Arrival-Date: Sun Apr 26 05:30:01 PDT 1998 >Last-Modified: Sat Jul 18 13:10:58 PDT 1998 >Originator: tmornini@infomania.com >Organization: >Release: 1.3b6 >Environment: SunOS sun630mp 5.5.1 Generic_103640-19 sun4m sparc SUNW,SPARCsystem-600 gcc version 2.8.1 >Description: I've noticed that since server-status became available, on my system the number of possible connection slots is always shown as 4 lines of 64, regardless of how I configure the server. It would certainly seem to make more sense to limit the slots shown to the max set in the config, thereby giving a visual sense of how close to maxing out you are. I also just noticed that apachectl fullstatus and apachectl status give identical output on my system, and these agree with the server-status URL. That is, they also show 256 slots, 4 lines of 64, and fullstatus and status do not differ as explained in man apachectl, i.e. details on current connections. My important config details: MinSpareServers 5 MaxSpareServers 75 StartServers 50 MaxClients 75 MaxRequestsPerChild 100000 SetHandler server-status order deny,allow deny from all allow from 199.182.37 allow from 127.0.0.1 I figured this was a general problem, until I searched the bug-reports, and I saw other's output that had different numbers of connection slots shown. I figured Apache always showed 256, and I was going to ask for a feature change. >How-To-Repeat: http://www.infomania.com/server-status You will need to let me know what IP address to allow access from. >Fix: Unfortunately, no. >Audit-Trail: From: Dean Gaudet To: Tom Mornini Cc: apbugs@hyperreal.org Subject: Re: mod_status/2138: mod_status always displays 256 possible connection slots Date: Sun, 26 Apr 1998 17:14:06 -0700 (PDT) I suppose yes this could be confusing. But there's a reason for it -- it has to do with graceful restarts. Suppose you were to change your MaxClients and then do a graceful restart. If you lower it you could possibly have children (gracefully exiting) numbered higher than the current MaxClients... so we'd need to keep some sort of history for MaxClients in order to figure out how much of the table to show. Dean From: Tom Mornini To: Dean Gaudet Cc: apbugs@hyperreal.org Subject: Re: mod_status/2138: mod_status always displays 256 possible connection slots Date: Sun, 26 Apr 1998 18:17:16 -0700 (PDT) On Sun, 26 Apr 1998, Dean Gaudet wrote: > I suppose yes this could be confusing. But there's a reason for it -- it > has to do with graceful restarts. Suppose you were to change your > MaxClients and then do a graceful restart. If you lower it you could > possibly have children (gracefully exiting) numbered higher than the > current MaxClients... so we'd need to keep some sort of history for > MaxClients in order to figure out how much of the table to show. Why not just show the current status correctly, and graceful shutdowns separately? It seems very unfortunate to display it strangely 99% of the time. How often would the scenario above happen in reality? -- Tom Mornini -- InfoMania Printing and Prepress State-Changed-From-To: open-suspended State-Changed-By: lars State-Changed-When: Sat Jul 18 13:10:58 PDT 1998 State-Changed-Why: I've supsended your report and marked it as change-request. Thanks for your suggestion. Class-Changed-From-To: sw-bug-change-request Class-Changed-By: lars Class-Changed-When: Sat Jul 18 13:10:58 PDT 1998 >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]