Jyri Virkki wrote:

> Please tell us more about the differences. Can you post diffs? 

The difference is in the LoadModule directives

e.g.,
        LoadModule authn_file_module libexec/mod_authn_file.so        --> 32 bit
        LoadModule authn_file_module libexec/amd64/mod_authn_file.so  --> 64 bit


> Are the differences limited to the httpd.conf file or do they extend
> to any other *.conf files in conf.d?

It is applicable to httpd.conf file. Other .conf files do not have 64 bit 
specific
location settings.

> As Sriram mentioned, separate .conf files are unfriendly, I'd rather
> not maintain duplicate files. Can the difference be factored out?

This can be done by passing a configuration parameter during server startup.
e.g., apachectl can be modified to pass 64bit config parameter.
        $HTTD -D64bit $ARGV

And httpd.conf file can be modified to include the 64 bit specific directives 
only
when this parameter is defined.
e.g.,

        <IfDefine !64bit>               
                LoadModule authn_file_module libexec/mod_authn_file.so
                LoadModule authn_dbm_module libexec/mod_authn_dbm.so
                LoadModule authn_anon_module libexec/mod_authn_anon.so
        </IfDefine>
        <IfDefine 64bit>
                LoadModule authn_file_module libexec/amd64/mod_authn_file.so
                LoadModule authn_dbm_module libexec/amd64/mod_authn_dbm.so
                LoadModule authn_anon_module libexec/amd64/mod_authn_anon.so
        </IfDefine>


This config parameter ( 64bit ) should be passed explicitly by the user if 
64-bit "httpd" is
invoked directly (not through apachectl).
e.g.,   %> /usr/apache2/2.2/bin/amd64/httpd -D64bit -k start

I'm not aware of any other ways of handling this.


-- Seema.

Reply via email to