Frank,

Thanks for your response, I've just realized I was short on the version number. Its actually 1.99_16 that its running, under RHEL4. I've spoken to Rackspace (the hosting provider) about upgrade to a newer version and they're telling me that will break the support agreement and cost extra money and then other stuff will become unsupported. :( .... Rackspace also told me "The backpatched mod_perl 1.99 is stable, which is why RedHat packages it." -- something doesn't seem right about this though. Is this BS they're feeding me? If whatever is in there is not good for a production environment then I definitely want to take steps to deal with it the right way. So I guess I'm asking if 1.99_16 makes a difference compared to 1.99 (that I erroneously quoted before) and if you have any idea what Rackspace might mean about Redhat "backpatching" mod_perl. Thanks again.
-Chris

Frank Wiles wrote:

On Thu, 29 Jun 2006 10:12:13 -0400
Chris Hagglund <[EMAIL PROTECTED]> wrote:

I am looking for information on how to get mod_perl 1.99 under
apache2 (is this a screwball setup? Its with plesk 7.5 on redhat) to
send STDERR to the vhost error_log instead of the main apache
error_log.

I have mod_cgi scripts which write to the vhost error_log via STDERR with no problem, but for some reason the mod_perl code is putting
stuff into the main error_log. On my old server, mod_perl 1.29 and
apache 1.3, mod_perl STDERR output goes to the vhost error_log with
no problems. Any information is on how to deal with this is
appreciated. Also if there is a searchable archive of this list can
someone please point me to it? Thanks for any information.

mod_perl 1.99 was a development release and shouldn't be used in production at all. You're going to want to upgrade to mod_perl 2.0.2 and I would wager your problem will be solved. You can find searchable archives at the bottom of this page:
 http://perl.apache.org/maillist/modperl.html

---------------------------------
  Frank Wiles <[EMAIL PROTECTED]>
  http://www.wiles.org
---------------------------------

Reply via email to