Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 8713 invoked by uid 500); 12 Apr 2000 18:03:15 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 8683 invoked from network); 12 Apr 2000 18:03:13 -0000 Date: Wed, 12 Apr 2000 11:03:12 -0700 (PDT) From: dean gaudet To: new-httpd@apache.org Subject: Re: server-status In-Reply-To: <200004121756.KAA31503@trudge.engr.sgi.com> Message-ID: X-comment: visit http://arctic.org/~dean/legal for information regarding copyright and disclaimer. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Wed, 12 Apr 2000, Mike Abbott wrote: > Comments? in another program i wrote i ended up putting lots of stats in its status page, for each of its equivalent to modules, but the page eventually got so unweildy i realised i needed to break it up a bunch. what might be more appropriate is a status page hierarchy. and... i once again point folks to linux-kernel archives, the last two weeks they've been discussing the /proc hierarchy, which is both a status reporting, and configuration interface to the kernel. they're talking about new methods of configuring /proc. of course there's also the tie in to SNMP... i kind of like the /proc type interface because it's essentially unformatted, and relies on external formatters (which you know as netstat, vmstat, uptime, top, ...) -dean