[freeside] FreezeThaw

[ivan]

On Mon, Jun 12, 2000 at 11:10:10PM -0500, Donald L Greer Jr. wrote:
> 
> 
> Turtle wrote:
> 
> > [...]>
> > >suEXEC comes with the Apache distribution, is not normally installed or
> > >enabled by default, and requires modification of your Apache configuration
> >
> > >files.  This is documented in <http://www.apache.org/docs/suexec.html>,
> > >which is linked to _suEXEC_ in the installation instructions.
> >
> > Aah.  I see.  Ok thanks.  That brings up another problem too... I can't update
> > to a new apache installation unless I completely change the layout of my httpd.conf
> > file, well, at least the modules section.  I am not quite sure how to do that
> > and cannot bring down my webserver to do that or to recompile it, so I'm kindof
> > stuck with the current version on my other server.  However, that's completely
> > unrelated to freeside. :-)
> >
> 
> I found that the suexec would require a similar rewrite on my server,
> so I chose to use perl's suExec.

I believe you're thinking of perl's setuid emulation, not "perl's suExec".

> For the moment, this is an experimental server, but I don't see why this could be used on the final
> production server as well.
>   I think this is mentioned in the docs as an alternative to suExec.
>  Ivan?  Any comment?

Other than performance, I don't see any reason not to use it in a
production server. 

It's pretty much equivalent to suEXEC in terms of performance; you still
need to launch a separate process for each script.  Debugging is probably
easier with Perl's setuid emulation; since suEXEC dies silently on errors,
you wind up with unexplained "Premature end of script headers" if
anything's configured incorrectly.

-- 
meow
_ivan