Stas Bekman wrote:
OK, that's better :) But doesn't Apache start a new process then?
No -- we're only running one process (-D ONE_PROCESS) -- see Apache/TestServer.pm ;)
You mean when debugging? Because normally we don't start one process.
It's only the case if $self->{run}->{opts}->{'one-process'} is true.
Hmm. Where would that get set?
It's not. Unless you pass this option or you run coverage testing. on worker mpm, we have two processes.
Both the full test suite and the bug reporting skeleton definitely only have one Apache.exe running in my Task Manager. However, I notice if I watch it carefully that a second Apache.exe appears very briefly and then disappears again.
a bug in Apache may be? May be check the winnt mpm source?
The error_log only contains:
[Tue Dec 14 15:06:47 2004] [notice] Child 3844: Child process is running
[Tue Dec 14 15:06:47 2004] [notice] Child 3844: Acquired the start mutex.
[Tue Dec 14 15:06:47 2004] [notice] Child 3844: Starting 50 worker threads.
[Tue Dec 14 15:06:47 2004] [debug] child.c(684): Child 3844: Worker thread 0 starting.
(and another 49 message like the last one, since ThreadsPerChild is 50)
BTW, do we still need this hack? I thought it was supposed to be fixed in 2.0.50, no? (talking about the need to run as many threads as vhosts)
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
