Received: (qmail 6402 invoked by uid 2012); 23 Jul 1998 16:47:38 -0000
Message-Id: <19980723164738.6401.qmail@hyperreal.org>
Date: 23 Jul 1998 16:47:38 -0000
From: Scott Rose <rose@cs.washington.edu>
Reply-To: rose@cs.washington.edu
To: apbugs@hyperreal.org
Subject: Startup suexec message is missing
X-Send-Pr-Version: 3.2

>Number:         2678
>Category:       suexec
>Synopsis:       Startup suexec message is missing
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Jul 23 09:50:01 PDT 1998
>Last-Modified:  Thu Jul 23 15:46:41 PDT 1998
>Originator:     rose@cs.washington.edu
>Organization:
>Release:        1.3.1
>Environment:
Linux 2.0.33. gcc 2.7.2.3. libc 5.3.12.
>Description:
I can see in the release notes comments about the message that is printed if 
suexec is active being managed differently-- in 1.3.0, it was a simple fprintf() to 
STDERR. But now it seems to be entirely gone-- it isn't printed, it isn't in my
binary as a string, and it doesn't seem to be anywhere in the sources. That
complicates debugging suexec.
>How-To-Repeat:

>Fix:

>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: coar
State-Changed-When: Thu Jul 23 15:46:41 PDT 1998
State-Changed-Why:

The message isn't missing, it's just been moved to the
error_log.  The fprintf() call was causing problems when
a suexec-enabled server was run in inetd mode.  The text of
the message has been changed, too.

>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]