View Full Version : suphp on etch
daveb
17th February 2008, 02:08
After looking over the new howto for suphp install-suphp-on-various-linux-distributions-for-use-with-ispconfig-2.2.20-and-above (http://www.howtoforge.com/install-suphp-on-various-linux-distributions-for-use-with-ispconfig-2.2.20-and-above)
for the debian portion I noticed that their was no mention of changing any lines in "mod_suphp.c" as their was on the previous howto
suphp_debian_etch_ispconfig (http://www.howtoforge.com/suphp_debian_etch_ispconfig)
I have previously installed suphp according to the older howto. So my question would be should I recompile? and or what did changing those lines accomplish, any thoughts?
falko
17th February 2008, 19:53
I have previously installed suphp according to the older howto. So my question would be should I recompile? and or what did changing those lines accomplish, any thoughts?
You don't need to recompile.
The changed line made it possible that you could place the suPHP directives directly in a vhost, without a <Directory> directive. The new ISPConfig version writes a <Directory> stanza, that's why the source code change isn't needed anymore. :)
daveb
17th February 2008, 19:58
Thanks Falko, Had to ask since I couldn't find anything really regarding that when I looked over the readme for suphp last night.
Hans
19th February 2008, 09:09
@Falko,
The http://www.howtoforge.com/install-suphp-on-various-linux-distributions-for-use-with-ispconfig-2.2.20-and-above is really usefull!
Thanks for this work again, it will help a lot of ISPConfig administrators, who want to use suphp on their ISPConfig server.
I think it is a good idea not only to explain howto install suphp, but also how to configure it for different Linux distributions, like the /etc/suphp.conf file for example.
I mention this, because after installation configuration is still necesarry.
Just one example, if you install suphp on Debian, you need to change wwwrun into www-data within /etc/suphp.conf. The permissions and handlers within /etc/suphp.conf need to be configured as well.
falko
20th February 2008, 19:06
Just one example, if you install suphp on Debian, you need to change wwwrun into www-data within /etc/suphp.conf. The permissions and handlers within /etc/suphp.conf need to be configured as well.
The new ISPConfig versions (since 2.2.20) come with their own /etc/suphp.conf, so you don't have to modify that file. :)
Hans
27th February 2008, 12:45
The new ISPConfig versions (since 2.2.20) come with their own /etc/suphp.conf, so you don't have to modify that file. :)
Ok then, i understand that the default /etc/suphp.conf is not used anymore.
Can you tell me where the suphp.conf is, which is used form ispconfig 2.2.20 and up?
falko
28th February 2008, 20:03
It's /etc/suphp.conf. The old one got copied to /etc/suphp.conf_date.
Hans
28th February 2008, 20:33
Thanks Falko,
One more question:
I understand that /etc/suphp.conf will be overwritten everytime we perform an update for ispconfig?
falko
29th February 2008, 15:09
Yes, that's true.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.