gmane.comp.php.suphp.general

suPHP logging

Tomáš Kadlec — 2008-11-27T07:33:39

Hello, with Apache httpd 2.2 there is no problem to log to syslog ErrorLog and Custom Logs (using pipes). I am wondering if there is a way how to redirect log of suphp module to syslog also (or at least to ErrorLog). Thanks in advance. Tomas Kadlec

Use auto_prepend_file

Samuel Hassine — 2008-11-24T22:05:27

Hi all, I have a little probleme here. Hope someone could help me. I want to use auto_prepend_file in a global php.ini file for multiple users. Each user have a different uid/gid and SuPHP executes scripts with uid of the owner. But the PHP file I wish to use in the auto_prepend_file directive is the same for all users. Is it possible to do this ? Best regards. Sam

Re: How to limit custom php.ini options

suphp — 2008-11-18T08:22:44

Thomas De Groote a écrit : Hello You can put the custom php.ini in a directory that is not accessible by your user. i.e.: Your DocumentRoot is /web/users/user1/www Put php.ini in /web/users/user1 The user should have to contact you to make changes to php.ini Patrick

How to limit custom php.ini options

Thomas De Groote — 2008-11-18T06:04:15

Hi all, I recently discovered the ability to have a custom php.ini when using suPHP (after using it for 5 years). Is there an option or a way to limit which settings can be changed in the custom php.ini? I do not want my users to change the memory or file upload settings, but do want to offer them some other options (globals_on etc). Thomas

Allowoverride

Leonardo Costa — 2008-11-17T23:50:38

Hi, I'm new in list, I searched here something about my problem but not found. I have working many servers with apache, php and suphp. With the current code, if the user want set suphp (like suPHP_ConfigPath) on .htaccess, httpd.conf need have the option "Allowoverride Options". I want to permit the user to config "Options", to configure "Directory" in Apache but not "suPHP_ConfigPath". Has some way? For example, I want the user (.htacces) can set like this: Options Indexes FollowSymLinks But not: suPHP_ConfigPath /home/user/public_html The configuration AllowOverride permit or not both sets. Thank you,

Installation Problems with suphp 0.6.3 Under Irix 6.5

Steve Johns — 2008-11-16T22:44:29

_______________________________________________ suPHP mailing list suPHP-qhrM8SXbD5JCREYaNQg7v6nAVvkbxe8d< at >public.gmane.org http://lists.marsching.com/mailman/listinfo/suphp

Re: Multiple Users

Hugo Monteiro — 2008-11-10T10:33:11

As long as user1 is the owner of what's in /home/www.test.com/, but not in /home/www.test.com/user2, and user2 is the owner of what's in /home/www.test.com/user2, i can't see why it shouldn't work. In the case you need that one or both users need to write files that are owned by the other one, you can always put both users into the same system group and use allow_file_group_writeable to tune your needs. Regards, Hugo Monteiro.

Multiple Users

Dustin Schuemann — 2008-11-09T23:44:35

_______________________________________________ suPHP mailing list suPHP-qhrM8SXbD5JCREYaNQg7v6nAVvkbxe8d< at >public.gmane.org http://lists.marsching.com/mailman/listinfo/suphp

Exclude repertory with suphp / Horde / Plesk

Laurent Rathle — 2008-11-04T08:54:30

Hello, I use suphp on a Plesk install and can't use the webmail Horde since it is installed in /usr/share/psa-horde with root as UID and GID. Is there a possibility to exclude this repertory from suphp ? If not, I've been suggested to make a sym link to /usr/share/psa-horde in /var/ www and to change the apache settings so it use this location to access to Horde. Will it work easily ? Last possibility I've looked for was to make a fresh install of Horde (or any other webmail) but this time in /var/www and with www-data for UID and GID. Which solution would be the best ? Thank you...

suPHP / mod_php configuration

Jack Bates — 2008-10-03T21:32:27

_______________________________________________ suPHP mailing list suPHP-qhrM8SXbD5JCREYaNQg7v6nAVvkbxe8d< at >public.gmane.org http://lists.marsching.com/mailman/listinfo/suphp

FW: Problem installing and configuring suPHP on Debian4.0Etch

2008-10-02T18:28:43

Still no luck... What logs could I review/provide to help pinpoint the problem. I have noticed the suPHP log folder remains empty Thanks, j. -----Original Message----- From: jamie-vpOEi5smH4AUy0mseJX/+UEOCMrvLtNR< at >public.gmane.org [mailto:jamie-vpOEi5smH4AUy0mseJX/+UEOCMrvLtNR< at >public.gmane.org] Sent: 02 October 2008 18:03 To: 'Jeremy Chadwick' Cc: 'Daniel Llewellyn'; 'suphp-qhrM8SXbD5JCREYaNQg7v6nAVvkbxe8d< at >public.gmane.org' Subject: RE: [suPHP] Problem installing and configuring suPHP on Debian 4.0 Etch Thank you Jeremy I do understand and appreciate your comments and Daniel's assistance on this matter. I stand corrected on the 'Linux' thing, I will read digest and feedback to you. Kind regards, j. -----Original Message----- From: Jeremy Chadwick [mailto:suphp-Usqv9Coizssf82w2karJbQ< at >public.gmane.org] Sent: 02 October 2008 16:49 To: jamie-vpOEi5smH4AUy0mseJX/+UEOCMrvLtNR< at >public.gmane.org Cc: 'Daniel Llewellyn'; suphp-qhrM8SXbD5JCREYaNQg7v6nAVvkbxe8d< at >public.gmane.org Subject: Re: [suPHP] Problem installing and configuring suPHP on Debian 4.0 Etch The reason Daniel isn't spelling it out for you in black and white is because he wants you to learn. Copy-pasting what someone tells you teaches you nothing. :-) Secondly, the syntaxes you're being given and are using are flat out wrong. You need to pay more attention to what you're doing and read some documentation (Apache and suPHP both). For every handler-name entry in the [handlers] section of suphp.conf, you need to tell the mod_suphp Apache module what handler-name to associate itself with (so PHP will interpret the data). You also have to tell Apache what file extension to map to what handler-name. For example, this would spawn the php5-cgi binary interpreter via suPHP when Apache sees requests for a .php5 extension: suphp.conf: [handlers] i-like-rice=php:/usr/bin/php5-cgi httpd.conf: suPHP_Engine on AddHandler i-like-rice .php5 suPHP_AddHandler i-like-rice Now, STOP RIGHT HERE and read those lines VERY CAREFULLY. Notice how many parameters suPHP_AddHandler is being given, and where the file extension is being defined. Just slow down and read them over a few times. I also urge people to use actual MIME types in their suphp.conf and httpd.conf, as AddHandler falls under mod_mime, and that makes me often wonder if you need a real MIME type and not just a string... suphp.conf: [handlers] application/x-httpd-php=php:/usr/bin/php5-cgi httpd.conf: suPHP_Engine on AddType application/x-httpd-php .php suPHP_AddHandler application/x-httpd-php Finally, this is not a "Linux" thing. You're working with two specific pieces of software: suPHP and Apache. Neither of these are Linux, as they both can run on BSD, Solaris, IRIX, or even Windows.

Re: Problem installing and configuring suPHP on Debian4.0Etch

2008-10-02T17:03:04

Thank you Jeremy I do understand and appreciate your comments and Daniel's assistance on this matter. I stand corrected on the 'Linux' thing, I will read digest and feedback to you. Kind regards, j. -----Original Message----- From: Jeremy Chadwick [mailto:suphp-Usqv9Coizssf82w2karJbQ< at >public.gmane.org] Sent: 02 October 2008 16:49 To: jamie-vpOEi5smH4AUy0mseJX/+UEOCMrvLtNR< at >public.gmane.org Cc: 'Daniel Llewellyn'; suphp-qhrM8SXbD5JCREYaNQg7v6nAVvkbxe8d< at >public.gmane.org Subject: Re: [suPHP] Problem installing and configuring suPHP on Debian 4.0 Etch The reason Daniel isn't spelling it out for you in black and white is because he wants you to learn. Copy-pasting what someone tells you teaches you nothing. :-) Secondly, the syntaxes you're being given and are using are flat out wrong. You need to pay more attention to what you're doing and read some documentation (Apache and suPHP both). For every handler-name entry in the [handlers] section of suphp.conf, you need to tell the mod_suphp Apache module what handler-name to associate itself with (so PHP will interpret the data). You also have to tell Apache what file extension to map to what handler-name. For example, this would spawn the php5-cgi binary interpreter via suPHP when Apache sees requests for a .php5 extension: suphp.conf: [handlers] i-like-rice=php:/usr/bin/php5-cgi httpd.conf: suPHP_Engine on AddHandler i-like-rice .php5 suPHP_AddHandler i-like-rice Now, STOP RIGHT HERE and read those lines VERY CAREFULLY. Notice how many parameters suPHP_AddHandler is being given, and where the file extension is being defined. Just slow down and read them over a few times. I also urge people to use actual MIME types in their suphp.conf and httpd.conf, as AddHandler falls under mod_mime, and that makes me often wonder if you need a real MIME type and not just a string... suphp.conf: [handlers] application/x-httpd-php=php:/usr/bin/php5-cgi httpd.conf: suPHP_Engine on AddType application/x-httpd-php .php suPHP_AddHandler application/x-httpd-php Finally, this is not a "Linux" thing. You're working with two specific pieces of software: suPHP and Apache. Neither of these are Linux, as they both can run on BSD, Solaris, IRIX, or even Windows.

Re: Problem installing and configuring suPHP on Debian4.0Etch

Jeremy Chadwick — 2008-10-02T15:49:00

The reason Daniel isn't spelling it out for you in black and white is because he wants you to learn. Copy-pasting what someone tells you teaches you nothing. :-) Secondly, the syntaxes you're being given and are using are flat out wrong. You need to pay more attention to what you're doing and read some documentation (Apache and suPHP both). For every handler-name entry in the [handlers] section of suphp.conf, you need to tell the mod_suphp Apache module what handler-name to associate itself with (so PHP will interpret the data). You also have to tell Apache what file extension to map to what handler-name. For example, this would spawn the php5-cgi binary interpreter via suPHP when Apache sees requests for a .php5 extension: suphp.conf: [handlers] i-like-rice=php:/usr/bin/php5-cgi httpd.conf: suPHP_Engine on AddHandler i-like-rice .php5 suPHP_AddHandler i-like-rice Now, STOP RIGHT HERE and read those lines VERY CAREFULLY. Notice how many parameters suPHP_AddHandler is being given, and where the file extension is being defined. Just slow down and read them over a few times. I also urge people to use actual MIME types in their suphp.conf and httpd.conf, as AddHandler falls under mod_mime, and that makes me often wonder if you need a real MIME type and not just a string... suphp.conf: [handlers] application/x-httpd-php=php:/usr/bin/php5-cgi httpd.conf: suPHP_Engine on AddType application/x-httpd-php .php suPHP_AddHandler application/x-httpd-php Finally, this is not a "Linux" thing. You're working with two specific pieces of software: suPHP and Apache. Neither of these are Linux, as they both can run on BSD, Solaris, IRIX, or even Windows.

Re: Problem installing and configuring suPHP on Debian 4.0Etch

2008-10-02T15:33:51

Sorry for being a bit thick but I'm fairly new to the world of Linux are you suggesting adding the following line to suphp.conf: php5-script=php:/usr/bin/php5-cgi If this is correct then It still fails to resolve the problem. Kind regards, j. -----Original Message----- From: Daniel Llewellyn [mailto:diddledan-gM/Ye1E23mwN+BqQ9rBEUg< at >public.gmane.org] Sent: 02 October 2008 15:45 To: jamie-vpOEi5smH4AUy0mseJX/+UEOCMrvLtNR< at >public.gmane.org Cc: suphp-qhrM8SXbD5JCREYaNQg7v6nAVvkbxe8d< at >public.gmane.org Subject: Re: [suPHP] Problem installing and configuring suPHP on Debian 4.0 Etch check this line and these three lines these two statements should help with your diagnosis.. suphp knows what to do with x-httpd-php, but not php5-script

Re: Problem installing and configuring suPHP on Debian 4.0Etch

Daniel Llewellyn — 2008-10-02T14:44:51

check this line and these three lines these two statements should help with your diagnosis.. suphp knows what to do with x-httpd-php, but not php5-script

Newbie question

Laurent Rathle — 2008-10-02T09:26:52

Hello, I run into problem when I try to install Joomla on a server where Plesk is installed. I've heard that suphp could help me with that. It is mostly permissions problems to install the software or his components. Is it true and is there any documentation which would help me to set up suphp and Plesk ? Thank you,

Re: Problem installing and configuring suPHP on Debian 4.0Etch

2008-10-02T08:33:32

Hi David, thanks for your prompt reply. I'm new to all this, how would I fix the issues you have highlighted? j. -----Original Message----- From: Daniel Llewellyn [mailto:diddledan-gM/Ye1E23mwN+BqQ9rBEUg< at >public.gmane.org] Sent: 02 October 2008 01:05 To: jamie-vpOEi5smH4AUy0mseJX/+UEOCMrvLtNR< at >public.gmane.org Cc: suphp-qhrM8SXbD5JCREYaNQg7v6nAVvkbxe8d< at >public.gmane.org Subject: Re: [suPHP] Problem installing and configuring suPHP on Debian 4.0 Etch On Wed, Oct 1, 2008 at 10:42 PM, public.gmane.org> wrote: suphp.conf: hosts.conf: .php5 files won't execute with suPHP (hasn't been told to execute them, but does know what to execute them with) .php files won't execute with suPHP (has been told to execute them, but doesn't know what to execute them with)

Re: Problem installing and configuring suPHP on Debian 4.0Etch

Daniel Llewellyn — 2008-10-02T00:04:41

suphp.conf: hosts.conf: .php5 files won't execute with suPHP (hasn't been told to execute them, but does know what to execute them with) .php files won't execute with suPHP (has been told to execute them, but doesn't know what to execute them with)

Re: suphp uploaded file permissions

Roland Tapken — 2008-10-01T22:48:00

_______________________________________________ suPHP mailing list suPHP-qhrM8SXbD5JCREYaNQg7v6nAVvkbxe8d< at >public.gmane.org http://lists.marsching.com/mailman/listinfo/suphp

Problem installing and configuring suPHP on Debian 4.0 Etch

2008-10-01T21:42:22

_______________________________________________ suPHP mailing list suPHP-qhrM8SXbD5JCREYaNQg7v6nAVvkbxe8d< at >public.gmane.org http://lists.marsching.com/mailman/listinfo/suphp

Re: SuPHP recursive forking

John Lightsey — 2008-09-29T15:10:04

My understanding is that in the past FreeBSD wouldn't allow you to install the PHP 4 CLI and CGI binaries simultaneously, so it's still possible on an older FreeBSD machine that /usr/local/bin/php is the CGI binary. The way we install it is a legacy issue originally intended to deal with PHP4's inability to install the PHP CGI and PHP CLI binaries in the same location. PHP4 installs both the CLI and CGI binaries as just "php". The PHP development team corrected that problem with PHP5, but we have many customers who still want to use 4 and have applications that are expecting the CGI and CLI binaries to be installed in those specific locations. In the longer run we'd like to get these custom PHP installs out of the system paths entirely and just use a symlink for one version of the the CLI binary into /usr/bin/php. If we're handing out blame though, I'd say that the bigger issue is that there shouldn't be separate CLI and CGI binaries to begin with. PHP has its own legacy problems to deal with though and this seems to be one of them. Of course, deciding that "php" will only refer to the CLI binary after years of using it to refer to both the CLI and CGI binaries isn't a very safe approach to begin with. They could have called it php-cli with PHP5 to avoid these name collisions. J.D.