Max wrote: > Hey Dave > > Thanks for your reply. I'm not entire sure if this solution can be > easily applied to my setup, however I have learned that my httpd.conf > file does have the setting already there for each user. The trouble > is, these settings are in a virtualhost block for each user, and > suPHP does not appear to be picking them up - it only seems to go for > a global setting if one exists, and none other if it doesn't. I'm > wondering if there's anything I can do to make suPHP pick up the > 'suPHP_UserGroup' setting inside a VirtualHost in an apache config file? Which version of suPHP are you using? It should work fine from at least 0.6.2.
> > Cheers, > Max > > Dave Ingram wrote: >>> Hello >>> >>> I have a question about the 'suPHP_UserGroup' setting. Without it, >>> apache gives internal server errors for php scripts. And it only >>> seems to work if I set the owner of the script as the username and >>> groupname. In a multi-user environment, each individual user will >>> own their own scripts, so I am wondering if there is a simple way of >>> setting it to be the default owner of the script? Or otherwise, how >>> can I manage this setting in a multi-user environment? >>> >>> I feel as though I am missing something here. >>> >> Argh, sorry -- I missed the point completely. I think you could use >> "owner mode", perhaps. >> >> I run a shared hosting environment with many users in different >> (sometimes overlapping) groups. Each group "owns" a subdirectory on the >> webserver. I have a separate suPHP_UserGroup setting for each directory >> (with suPHP in "force" mode), in addition to the patch I pointed you at. >> I then turn "check_parent_dir_owners" off, and "check_parent_dir_groups" >> on and set up "valid_parent_groups" appropriately (all settings provided >> by my patch). >> >> >> Dave >> >> >> > _______________________________________________ suPHP mailing list [email protected] https://lists.marsching.com/mailman/listinfo/suphp
