Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 76735 invoked by uid 500); 14 Apr 2002 11:37:45 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 76724 invoked from network); 14 Apr 2002 11:37:45 -0000 Date: Sun, 14 Apr 2002 13:38:25 +0200 (CEST) From: Sascha Schumann X-X-Sender: sas@eco.foo To: Jon Travis Cc: "William A. Rowe, Jr." , "dev@apr.apache.org" Subject: Re: Unix missing fd 0..2, Win32 service missing stdin/out/err handles In-Reply-To: <20020414013057.A10524@covalent.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > As I described, it would be possible for a user to close those > descriptors before doing something like say, opening an SDBM. If > they then try to _write_ to those (via something like write() to > stderr), then that is a programming error which we should not be > trying to solve. Not necessarily. The daemon might use a third-party library which writes diagnostic messages to stderr (something like Oracle's libs). Or even worse, the user might be running the application on FreeBSD where malloc(3) writes messages to stderr, if configured to do so. There are probably more cases where this can happen which the app's author cannot influence. Supplying module authors with a function which addresses this issue makes sense from that perspective. - Sascha Experience IRCG http://schumann.cx/ http://schumann.cx/ircg