Jeff Trawick wrote:
> Stas Bekman <[EMAIL PROTECTED]> writes:
>
>
>>Hmm, why do I get this warning on stop:
>>
>>WARNING: MaxClients (10) is not an integer multiple
>> of ThreadsPerChild (3), lowering MaxClients to 9
>> for a maximum of 3 child processes,
>>httpd (no pid file) not running
>>
>>I do get it on start as well, which is expected, but why on stop?
>
>
> The config file is read during stop processing now ("apachectl stop"
> calls "httpd -k stop"). One benefit is that if you move your pidfile
> to the non-default location it will be found without you having to
> edit apachectl.
That's a dangerous change. Because:
1. if httpd.conf is modified after the server has started and something
is broken, it's impossible to stop the server. I've just tested, it'll
just keep on running. The only way to stop it is to kill(1).
2. the reparse of the config file may have side effects. e.g. in
mod_perl we embed Perl code in httpd.conf, mainly used for creating
complex and big configuration file, using databases, etc. It's most
likely not desirable to run the code on server stop. At least we need to
have some flag to skip the run on stop.
p.s. if this change is becoming permanent, shouldn't it eliminate the
need for specifying the location of a pidfile in apachectl?
__________________________________________________________________
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
