Mailing-List: contact apache-bugdb-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: apache-bugdb@apache.org
Date: 18 Jan 2001 07:27:55 -0000
Message-ID: <20010118072755.65282.qmail@apache.org>
To: apache-bugdb@apache.org, msq-apache@msquared.com.au, slive@apache.org
From: slive@apache.org
Subject: Re: suexec/7089: suexec not executed in VirtualHost with same
 User/Group as main server

[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database 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!     ]


Synopsis: suexec not executed in VirtualHost with same User/Group as main server

State-Changed-From-To: open-analyzed
State-Changed-By: slive
State-Changed-When: Wed Jan 17 23:27:55 PST 2001
State-Changed-Why:
This is the expected behaviour.  Suexec is only enabled
if the user or group specified is different than the
one for the main server.  In my opinion, this is the
most natural thing to do, and should not be changed.
However, you are correct that this should be documented
in the suexec docs.  I've marked this report as
"analyzed" so we can look at it when we improve the
suexec documentation.

Thanks for using Apache!
Class-Changed-From-To: sw-bug-doc-bug
Class-Changed-By: slive
Class-Changed-When: Wed Jan 17 23:27:55 PST 2001