You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by The Gaijin <ga...@gci.net> on 2010/04/02 23:29:28 UTC
[users@httpd] Best Practices for mod_perl, mod_python, and mod_php
Hello -
I've inherited a system from our development group, and I've been
attempting to find information on recommended best practices for
running mixed mod_perl, mod_python and mod_php simultaneously on
Apache HTTPd using mod_prefork. Unfortunately, my Google-fu hasn't
produced much in the way of useful information, and I didn't find
anything specific to this on the Apache.org site.
My gut instinct is to break the installation into multiple instances,
each one servicing one of the mod_* services, but I'm hoping to
find hard information on whether or not this is correct.
Many thanks for your time,
R.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Best Practices for mod_perl, mod_python, and mod_php
Posted by Nilesh Govindarajan <li...@itech7.com>.
On 04/03/10 02:59, The Gaijin wrote:
>
> Hello -
>
> I've inherited a system from our development group, and I've been
> attempting to find information on recommended best practices for
> running mixed mod_perl, mod_python and mod_php simultaneously on
> Apache HTTPd using mod_prefork. Unfortunately, my Google-fu hasn't
> produced much in the way of useful information, and I didn't find
> anything specific to this on the Apache.org site.
>
> My gut instinct is to break the installation into multiple instances,
> each one servicing one of the mod_* services, but I'm hoping to
> find hard information on whether or not this is correct.
>
> Many thanks for your time,
>
> R.
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
I refrain from using any embedded interpreters. It doesn't give optimum
performance. Use mod_fcgid which will give you performance as well as
security since it possible to use suExec with mod_fcgid.
--
Nilesh Govindarajan
Site & Server Administrator
www.itech7.com
मेरा भारत महान !
मम भारत: महत्तम भवतु !
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Best Practices for mod_perl, mod_python, and mod_php
Posted by The Gaijin <ga...@gci.net>.
On 04/03/2010 12:59 AM, Nick Kew wrote:
>
> On 2 Apr 2010, at 22:29, The Gaijin wrote:
>
> Why would you expect to find anything specific?
Past experience (and the ESR article the sign-up page points to) suggest
that in most cases, someone else has already encountered an issue, or
done what you're trying to do, and documented the resolution, or
results. :)
> There's no
> recommended 'best practice' for using multiple scripting
> languages and environments: you could use the modules,
> or CGI/fastcgi, or proxy a backend. The only issue that arises
> from using more than one together is the risk of being bitten
> by some bug, but you won't know until you try.
So it seems - searches of the mod_python, mod_perl, and mod_php sites
didn't mention anything specifically one way or the other that I saw.
As I noted - it's a server mess I inherited from a different group, and
it's working, though there are reports of dysfunction. Unfortunately,
there's no hard evidence as to why it's failing. I'm putting in proper
monitoring, and looking at logging changes with an eye to "why?" But
there's nothing there I'd go to the list with However, my gut reaction
at running multiple interpreters in the same instance is "WTF?" and as
such, it seemed like a worthwhile parallel path to pursue.
> One thing I would suggest: either compile everything yourself
> or install everything from distro packages, don't mix-and-match.
> The latter might put you at higher risk of linking multiple
> versions of the same library.
Excellent suggestion - I'll have to go over the code they're using and
see what is being included and from where.
Nick & Nilesh: thank you both for your responses, your time and
suggestions are greatly appreciated. Apologies for the delayed response
- desktop died while sending, and work called.
R.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Best Practices for mod_perl, mod_python, and mod_php
Posted by Nick Kew <ni...@webthing.com>.
On 2 Apr 2010, at 22:29, The Gaijin wrote:
> I've inherited a system from our development group, and I've been
> attempting to find information on recommended best practices for
> running mixed mod_perl, mod_python and mod_php simultaneously on
> Apache HTTPd using mod_prefork. Unfortunately, my Google-fu hasn't
> produced much in the way of useful information, and I didn't find
> anything specific to this on the Apache.org site.
Why would you expect to find anything specific? There's no
recommended 'best practice' for using multiple scripting
languages and environments: you could use the modules,
or CGI/fastcgi, or proxy a backend. The only issue that arises
from using more than one together is the risk of being bitten
by some bug, but you won't know until you try.
One thing I would suggest: either compile everything yourself
or install everything from distro packages, don't mix-and-match.
The latter might put you at higher risk of linking multiple
versions of the same library.
--
Nick Kew
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org