[gobolinux-users] Placement of httpd modules

[Jonas Karlsson]

On Tue, 12 Sep 2006 16:11:43 +0200, MJ Ray <mjr at phonecoop.coop> wrote:

> "Jonas Karlsson" <jonka750 at student.liu.se> wrote: [...]
>> One of the former solutions, either one, is better, but which one
>> should be used?
>
> I'd prefer putting them under /System/Links/Libraries (share seems
> wrong, as they are binaries) and the default apache being configured to
> look there in its modules path.

Yes, I'd prefer that as well, when I think about it. I didn't like the  
share solution, but that was the only way I could think of for the modules  
to be reachable for httpd, without too long pathname (as  
/Programs/Foo/X.Y/share is a symlink to /System/Links/Shared).

Unfortunately I can't find a way to relocate where httpd looks for  
loadable modules. So I guess there has to be a long path in httpd.conf  
instead (anyone knows if one could use variables instead in httpd.conf?).

>
> Alternatively, debian systems has a program called something like
> a2enmod to symlink an apache module into the correct folder and all
> modules from that folder are loaded.  There's a similar program and
> folder for config sections.
>
The modules are always to be placed in /Programs/HTTPD/Current/odules, by  
default, and one could use unmanaged to symlink/copy the module there,  
even though unmanaged shouldn't be used to place files inside the  
/Programs structure (why?). The problem is that, with that approach, one  
has to symlink mod_php and similar everytime one recompiles httpd.

> Hope that helps,

It substantiated some of my thoughts...

-- 
/Jonas

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/