There are 2 options of course: 1) change the apache UID and GIU
2) install mod_cgi; that does allow suexec from what I have read. I don't know if the performance is the same though. On 29 Apr 2005 at 17:48, angie ahl wrote: > Thanks for trying though. The last hurdle's always the toughest one. Yeap that final 10% is a killer. Dp. > > > On 4/29/05, Dermot Paikkos <[EMAIL PROTECTED]> wrote: > > I really don't know but I was just trying to set up something > > similar here and noticed that under MP1 you certainly couldn't, see > > this article: > > http://perl.apache.org/docs/1.0/guide/install.html#Is_it_possible_to > > _r un_mod_perl_enabled_Apache_as_suExec_ > > > > And then I saw this on changes on MP2: > > > > "perchild > > > > The perchild MPM is similar to the worker MPM, but is extended with > > a mechanism which allows mapping of requests to virtual hosts to a > > process running under the user id and group configured for that > > host. This provides a robust replacement for the suexec mechanism. > > > > META: as of this writing this mpm is not working" > > > > It looks like suexec is not an option. There maybe an alternitive in > > the future though. Perhaps someone else with more knowledge on MP > > could answer your question better than I can. Dp. > > > > > > > > On 29 Apr 2005 at 17:38, angie ahl wrote: > > > > > So the scripts running under user apache and group apache, and the > > > site's files are suexec user/group myuser/myuser how do you write > > > files without permissions errors. > > > > > > Am I right in saying that if suexec were working right then the > > > uid and gid in the handler should be returning those for the > > > user/group that's in the suexec. > > > > > > If so then I guess it's not working. > > > > > > Really annoying as it's the final hurdle in well over a years > > > work. :( > > > > >
