The following reply was made to PR suexec/2761; it has been noted by GNATS.
From: Paul Bourke <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
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 [EMAIL PROTECTED]
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
