Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Wed, 7 Aug 2002 14:13:29 -0700
From: Justin Erenkrantz <jerenkrantz@apache.org>
To: dev@httpd.apache.org, rbb@covalent.net
Subject: Re: apachectl stop/restart running all init functions
Message-ID: <20020807211329.GF6479@apache.org>
Mail-Followup-To: Justin Erenkrantz <jerenkrantz@apache.org>,
	dev@httpd.apache.org, rbb@covalent.net
References: <00c401c23e40$846425a0$eb00000a@KOJ>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00c401c23e40$846425a0$eb00000a@KOJ>
User-Agent: Mutt/1.4i

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