Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 33206 invoked by uid 500); 27 Mar 2002 22:04:25 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 33193 invoked from network); 27 Mar 2002 22:04:25 -0000 Date: Wed, 27 Mar 2002 14:04:31 -0800 From: Aaron Bannert To: dev@httpd.apache.org Subject: Re: [PATCH] Removal of old, old SCOREBOARD_FILE fluff Message-ID: <20020327140431.F1154@clove.org> Mail-Followup-To: Aaron Bannert , dev@httpd.apache.org References: <200203271908.OAA01262@devsys.jaguNET.com> <20020327135051.F14500@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020327135051.F14500@apache.org> User-Agent: Mutt/1.3.23i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Wed, Mar 27, 2002 at 01:50:51PM -0800, Justin Erenkrantz wrote: > So if a third-party is interested in examining the scoreboard, they > have to do it either via a module or attach to the shared-memory > segment? > > Sounds fair enough... -- justin Nope, we don't lose that when we remove SCOREBOARD_FILE, AIUI. The right way for a third-party app to access the scoreboard at this point is to: 1) use a ScoreBoardFile directive to enable file-based scoreboard, then 2) write an app that uses APR (preferably the same APR install that httpd is using) and uses the apr_shm.h interface to access the scoreboard file. -aaron