ISPConfig3 : suphp on debian etch and a few other questions

[omry]

because you removed the usage of suPHP_UserGroup.
you said yourself it's more secure..

about updating:
once I update my source dir from svn, how do I upgrade the system?

[till]

because you removed the usage of suPHP_UserGroup.
you said yourself it's more secure..

No. The patch you applied has nothing to do with this. The patch is applaide as suphp does not read configuration settings that are written in a vhost instead of a directory directive.

about updating:
once I update my source dir from svn, how do I upgrade the system?

run:

ispconfig_update_from_svn.sh

on the shell as root user.

[omry]

Originally Posted by till

No. The patch you applied has nothing to do with this. The patch is applaide as suphp does not read configuration settings that are written in a vhost instead of a directory directive.



run:

ispconfig_update_from_svn.sh

on the shell as root user.

True, and since ispconfig puts the suphp section inside the vhost (and not inside a directory), the patch is needed.
without it apache bitches that it can't accept one of the directives (suPHP_UserGroup?) in the suphp clause.

about ispconfig_update_from_svn.sh :
looks like a more efficient way would be to do :
svn up
cd install
php -f update.php

from the directory where I checked up ispconfig from.

[omry]

Originally Posted by till

Thats not needed anymore. Please update to the latest ISPConfig 3 release from svn.

seems to be broken in svn.
I get this:

[Thu Sep 18 22:32:53 2008] [error] [client 79.178.130.180] No user or group set - set suPHP_UserGroup

[till]

Its not broken. The setup has just been switched to support the suphp packages that come with the linux distributions. As your suphp is compiled with "paranoid" mode, you will have to enable the suPHP_UserGroup line in the vhost master configuration file in /usr/local/ispconfig/server/conf/ again.

[omry]

aright, thanks.