Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of seanmckaybeck@gmail.com
 designates 74.125.83.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <519BD9D1.3010907@gmail.com>
References: 
 <CALP6eeadFJnQ7M54V1Jc3e5NuUy252EGweWbWNR6e=-vfYVdyQ@mail.gmail.com>
	<519BD9D1.3010907@gmail.com>
Date: Tue, 21 May 2013 15:52:53 -0600
Message-ID: 
 <CALP6eeb+kytB6b5gZtMyFA2sjjXvd4yyJu6a7XKjhJsJVoUKmg@mail.gmail.com>
Subject: Re: Get name of config file for module
From: Sean Beck <seanmckaybeck@gmail.com>
To: modules-dev@httpd.apache.org
Content-Type: multipart/alternative; boundary=089e016346449e1f2d04dd417825

--089e016346449e1f2d04dd417825
Content-Type: text/plain; charset=ISO-8859-1

Sorin,

Is there a way to figure out the name of the config file in code so I can
log it? Or even just the path to where it is.

Also, I'm confused because you said there is no such thing as a
module-specific configuration file, but then you said configuration files
can be split per-module. Does Apache just read out of httpd.conf on
start-up and in httpd.conf I would use the Include directive to include my
different configurations for each module?

Thanks


On Tue, May 21, 2013 at 2:32 PM, Sorin Manolache <sorinm@gmail.com> wrote:

> On 2013-05-21 21:36, Sean Beck wrote:
>
>> Hi all,
>>
>> I have written a module and now would like to log the name of the actual
>> config file being used by the module (there will be multiple modules on
>> the
>> server with their own config files. I looked through
>> https://httpd.apache.org/docs/**2.4/developer/modguide.html<https://httpd.apache.org/docs/2.4/developer/modguide.html>but am still
>> struggling to understand how Apache knows what the config file is for each
>> module and how I can check what the name of the actual name of the file is
>> for each module.
>>
>
> There is no such thing as a module-specific configuration file. In
> principle a single file could contain the configuration for all modules.
>
> The configuration files are split per-module for convenience only, in
> order to be able to activate modules independently.
>
> The configuration _directives_ are defined per-module (but actually
> nothing stops you from defining the same configuration directive in several
> modules).
>
> Apache defines a directive called "Include". This directive allows for the
> splitting of the entire configuration into several files. But from apache's
> point of view there is no correspondence between the files into which the
> configuration is split and the modules that define the directives found in
> those files.
>
> Sorin
>
>

--089e016346449e1f2d04dd417825--