On 19 Mar 2010, at 7:21 PM, Jeff Trawick wrote:
We came to the same conclusion ("don't") but via a different path.The LoadModule directive is already provided the global server_rec in the command_rec structure, whether or not it appears inside a <VirtualHost *>, by virtue of the EXEC_ON_READ flag. So using an expected server_rec for LoadModule doesn't seem to be the cause of Rich's problem symptom, and the usual code to disable a directive inside <VirtualHost > doesn't work/isn't needed. I don't know what caused the weird symptoms.
We uncovered a problem a while back with mod_perl, which in our case was being used to load some httpd config against a wildcard directory path, because the Include directive couldn't do it natively. As soon as an attempt was made to run a LoadModule from within a config that had been included with mod_perl's include functionality (the <Perl> tags), the server would segfault on startup. As soon as mod_perl's include functionality was removed from the config, everything worked again.
This problem inspired the wildcard directory fixes that were recently proposed for backport to v2.2. For us we had hacked around the lack of support for wildcard directories with mod_perl, and it was easier to fix the Include directive to support wildcards fully and remove our hack than dig to the bottom of the problem at the time.
Regards, Graham --
