Weird processes after upgrading to apache2

2004-06-13 Thread Kirk Strauser
I just started a trial switch to Apache 2 (from ports synched as of yesterday morning). It's going well for the most part, but I'm finding a few little weird things. For example, when I first start the server, ps returns a normal-looking list: # ps axw |grep httpd 38308 ?? Ss

Re: Weird processes after upgrading to apache2

2004-06-13 Thread Matthew Seaman
On Sun, Jun 13, 2004 at 02:02:44AM -0500, Kirk Strauser wrote: Those are the exact symptoms seen when httpd is run without the -DSSL argument. In other words, my little daemons seem to forget their name and their arguments after they've started. Note that despite the warning, the daemons

Re: Weird processes after upgrading to apache2

2004-06-13 Thread Kirk Strauser
At 2004-06-13T09:16:25Z, Matthew Seaman [EMAIL PROTECTED] writes: I suspect it's mod_perl causing the weirdness. Plain apache-2.0.49 works perfectly well for me serving up static html and some php. mod_perl is unusual though in that it has such a complete interface to the apache API. I

Re: Weird processes after upgrading to apache2

2004-06-13 Thread Matthew Seaman
On Sun, Jun 13, 2004 at 10:38:32AM -0500, Kirk Strauser wrote: At 2004-06-13T09:16:25Z, Matthew Seaman [EMAIL PROTECTED] writes: I suspect it's mod_perl causing the weirdness. Plain apache-2.0.49 works perfectly well for me serving up static html and some php. mod_perl is unusual

Re: Weird processes after upgrading to apache2

2004-06-13 Thread Kirk Strauser
At 2004-06-13T16:32:01Z, Matthew Seaman [EMAIL PROTECTED] writes: If you can get your hands on Practical mod_perl by Bekman and Cholet (O'Reilly -- http://www.oreilly.com/catalog/pmodperl/) there's two whole chapters about the differences between mod_perl and mod_perl2.0 Thanks for the