Received: (qmail 2365 invoked by uid 2012); 2 Aug 1998 07:30:40 -0000 Message-Id: <19980802073040.2364.qmail@hyperreal.org> Date: 2 Aug 1998 07:30:40 -0000 From: Paul Bourke Reply-To: paul@bourke.gen.nz To: apbugs@hyperreal.org Subject: suexec reporting X-Send-Pr-Version: 3.2 >Number: 2761 >Category: suexec >Synopsis: suexec reporting >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: support >Submitter-Id: apache >Arrival-Date: Sun Aug 2 00:40:00 PDT 1998 >Last-Modified: Mon Aug 3 00:33:55 PDT 1998 >Originator: paul@bourke.gen.nz >Organization: >Release: 1.3.1 >Environment: Irix 5.3 and 6.3 Indy and O2 Version 7.1 of the SGI compilers >Description: In the previous versions of Apache (1.3.0) one received a line apparently to stderr that httpd was runing with suexec, this message (a very comforting one) no longer seems to exist even though I believe suexec is running.... there are entries in the logs/cgi.log file each time a cgi is run. The online documentation for suexec seems out of date. The question: what's the correct way to now determine that suexec is being used. >How-To-Repeat: >Fix: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: coar State-Changed-When: Sun Aug 2 07:28:31 PDT 1998 State-Changed-Why: (This has already been reported and the answer is in the bugdb.) The previous stderr message was interfering with inetd mode operation, and so a modified version of the message is now emitted to the ErrorLog file instead. From: Paul Bourke To: coar@apache.org Cc: apbugs@apache.org Subject: Re: suexec/2761: suexec reporting Date: Mon, 3 Aug 1998 08:36:07 +1000 I realise from both the CHANGES file in the src tree and the previous report in bugdb that the message should go to the error log file.... indeed the error log was the first place I looked for the information. To reiterate - I'm assuming suexec is working because 1. I've been using it in the past and just updated from 1.3.0 to 1.3.1 2. correct looking messages are being written to cgi.log eg: [1998-08-02 19:45:10]: uid: (sweetie/sweetie) gid: (user/user) cmd: listadd.cgi [1998-08-02 19:45:42]: uid: (maverick/maverick) gid: (user/user) cmd: logit.cgi - There was nothing written to the error log except the normal startup message, eg: [Sun Aug 2 19:43:06 1998] [notice] Apache/1.3.1 (Unix) configured -- resuming normal operations >Synopsis: suexec reporting > >State-Changed-From-To: open-closed >State-Changed-By: coar >State-Changed-When: Sun Aug 2 07:28:31 PDT 1998 >State-Changed-Why: >(This has already been reported and the answer is in the >bugdb.) > >The previous stderr message was interfering with inetd >mode operation, and so a modified version of the message is >now emitted to the ErrorLog file instead. --------------------------------------------------------------------- Paul Bourke pdb@mhri.edu.au Brain Dynamics Research Unit http://www.mhri.edu.au/bdl/ Mental Health Research Institute Ph: 61 3 9389 2602 Locked Bag 11, Parkville Fax: 61 3 9387 5061 Victoria 3052, Australia Comment-Added-By: rse Comment-Added-When: Mon Aug 3 00:33:54 PDT 1998 Comment-Added: Yeah, you're right. There was a bug. The suEXEC message has to be of "notice" level because this level is treated differently for startup messages. Fixed for Apache 1.3.2 >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. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]