Martin MC Brown wrote:
> Hi,
>
>> Martin MC Brown wrote:
>>> You then configure the module configs to be included by editing the /
>>> etc/conf.d/apache file with the list of -D MODULE elements to include
>>> on the command line.
>> So editing the file is needed to enable a module/app?
>
> No, in each of the module specific files, you put the IfDefine:
>
> <IfDefine MODULE>
> ...
> </IfDefine>
>
> Then within the Apache conf, you load all the modules files, but only
> those with the defines are actually parsed.
>
Currently, modules-32.load and modules-64.load list the modules that will be
loaded.
Instead, should we move the individual LoadModule entries within the
modules-*.load files
to <modulename>-<32/64>.load and by default place them under some dir, say
"available-modules"
directory and then based on the user specified list, move the relevant .load
files to conf.d
dir or to say "enabled-modules" dir and add an entry within httpd.conf as
Include enabled-modules/*.load
similar to 'Include conf.d/*.conf"
How can this be handled for apachectl as there could be users who may not use
SMF ?
Pass the module list using -D option ?
> We can put the list of defined modules within SMF.
>
>> One of the goals here is that a baseline level of functionality must
>> "Just Work" merely by installing the relevant package(s).
>
> It will.
>
>> The current model of conf.d combined with including conf.d/*.conf from
>> the default configuration was selected for this purpose. It provides a
>> mechanism for packages [when applicable] to drop a file into conf.d
>> which means it is automatically configured without further interaction
>> required from the user (other than svcadm restart apache22).
>
>
> The only think you would need to do during installation is edit the
> SMF property to add the module. That should be possible, but I'd have
> to double check that.
>
Existing apache22 manifest supports "startup_options" property.
But additional property for listing the modules can be added.
Thanks,
Seema.
