Hi,
I have tried to set up suPHP (0.7.1 self compiled) on a development-server
(CentOS, Apache 2.2.3, PHP 5.3.3) using mod_userdir to force apache/php to run
php-files in user_dirs (/home/user/home/public_html) with the same user/rights
as its owner.
My problem: All php-Apps that create sessions get in conflict because all the
php-instances (runing as different users) seem to generate the SAME session-ids
which leads into identical session-file-names in /var/lib/php/sessions/. The
first php-app (or php-instance) successfully creates its session-file, but all
following apps (instances) end up with errors like ...
Warning: session_start(): open(/var/lib/php/session/sess_XXXXXX, O_RDWR)
failed: Permission denied (13) in /home/xxx/home/public_html/index.php on line X
Warning: Unknown: open(/var/lib/php/session/sess_XXXXXX, O_RDWR) failed:
Permission denied (13) in Unknown on line 0
Warning: Unknown: Failed to write session data (files). Please verify that the
current setting of session.save_path is correct (/var/lib/php/session) in
Unknown on line 0
Currently I have <Location>-Blocks that configure for each user_dir its own
php.ini (with suPHP_ConfigPath) in which i define different sessions-folders
for each app/user. That works but is an ugly workaround.
How do you fix/prevent/solve that? I was really surprised no one had that issue
before. There MUST be a better way.
Thanks and Greets,
Big D
PS: /home/user/home/public_html is no typo, we have a additional
"home"-directory for some other reasons, /home/user/ is still the $HOME/~ of
each user)
And little offtopic: How would force php/apache, running as its own user
(apache, www-data, depending on the OS), to set the rights of newly created
files always to 775 instead of 755 (which seems default)?
--
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
_______________________________________________
suPHP mailing list
[email protected]
https://lists.marsching.com/mailman/listinfo/suphp
