httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Bloom" <...@covalent.net>
Subject RE: apachectl stop/restart running all init functions
Date Wed, 07 Aug 2002 21:17:04 GMT
Good point.  I thought I had checked that, but I wasn't looking closely
enough.

Thanks.

Ryan

----------------------------------------------
Ryan Bloom
rbb@covalent.net           rbb@apache.org

> -----Original Message-----
> From: Justin Erenkrantz [mailto:jerenkrantz@apache.org]
> Sent: Wednesday, August 07, 2002 2:13 PM
> To: dev@httpd.apache.org; rbb@covalent.net
> Subject: Re: apachectl stop/restart running all init functions
> 
> On Wed, Aug 07, 2002 at 11:30:33AM -0700, Ryan Bloom wrote:
> >
> > I have a customer who has written a module that logs in the
post_config
> > phase that everything is working properly.  However, when they use
> > apachectl stop/restart they are seeing that log message, because the
-k
> > option doesn't terminate quickly enough.  This is very confusing.
Is
> > there a reason that we run the post_config phase for -k commands?
If
> > there is a reason, is there a way for module authors to determine
what
> > we are actually doing, e.g. starting, stopping, restarting, etc?
> 
> Hmm, looking at the code in HEAD, I don't believe that this is the
> case.  signal_server is called before the open_logs and post_config
> hooks are executed.  So, if this is indeed happening, something
> is very, very wrong.  -- justin


Mime
View raw message