Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Received: (qmail 81906 invoked from network); 10 Nov 2009 22:41:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Nov 2009 22:41:16 -0000 Received: (qmail 5732 invoked by uid 500); 10 Nov 2009 22:41:16 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 5680 invoked by uid 500); 10 Nov 2009 22:41:15 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 5670 invoked by uid 99); 10 Nov 2009 22:41:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Nov 2009 22:41:15 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [171.66.121.166] (HELO highwire.stanford.edu) (171.66.121.166) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Nov 2009 22:41:06 +0000 Received: from hw-durket.stanford.edu (hw-durket.Stanford.EDU [171.66.233.214]) by highwire.stanford.edu (Postfix) with ESMTP id C73198DCE for ; Tue, 10 Nov 2009 14:40:44 -0800 (PST) References: <4A874E3C.5090304@apache.org> In-Reply-To: <4A874E3C.5090304@apache.org> Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii Message-Id: <61C5FEB8-474F-4571-8EB1-5CFA0D2D53B4@highwire.stanford.edu> Content-Transfer-Encoding: quoted-printable From: Michael Durket Subject: post-config phase question Date: Tue, 10 Nov 2009 14:40:44 -0800 To: modules-dev@httpd.apache.org X-Mailer: Apple Mail (2.1077) X-Virus-Checked: Checked by ClamAV on apache.org Based on the few books that describe Apache module writing and a = presentation that I've found on the web from an Apache conference, the advice to = module=20 writers is to remember that Apache calls the post-config phase twice - = once=20 while it's checking its configuration files, and then when it's ready to = start up it discards all that and calls post-config again to really set things = up. But it appears to me (via tracing I've done in my own module) that = post-config is actually called once at configuration file checking time, and then = once per=20 server process start (we're using MPM here) during the second (actual = Apache startup phase). Is this correct?