On Wed, 2003-12-10 at 01:04, Stas Bekman wrote: > As our test suite grows it takes more and more time to start the server, the > worker mpm almost always fail to start within 60 secs on my machine (which is > pretty fast). And now we get reports from users who run prefork and it takes > 68 secs to start.
I constantly hover between 55-65 seconds, so my local copy has been patched for 90secs for quite a while already ;-) > So I'd suggest to make the default per server mpm and not one for all and go > with 120 secs for prefork and 180 worker/winnt. If it sometimes takes more > than 90 secs to start worker on my machine, I can see it hitting 3 minutes on > a slower machine. > > Ideally there should be no timeout at all, if we could deterministically > detect a failure in the server startup, but we weren't quite successful at it > so far. Well, until we can do that reliably, I am completely in favor of a high(er) timeout > __________________________________________________________________ > 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] -- -------------------------------------------------------------------------------- Philippe M. Chiasson /gozer\@(cpan|ectoplasm)\.org/ 88C3A5A5 (122FF51B/C634E37B) http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3 A5A5 Q: It is impossible to make anything foolproof because fools are so ingenious. perl -e'$$=\${gozer};{$_=unpack(P7,pack(L,$$));/^JAm_pH\n$/&&print||$$++&&redo}'
signature.asc
Description: This is a digitally signed message part
