To solve the second problem (Apache::Icon not loading its directives properly), I ended up commenting out all the "AddModule" statements as well as the "ClearModuleList" statement in the httpd.conf fiile. I don't really know why this fixed the problem, but I suppose it's related to having statically compiled all the basic modules directly into the httpd binary. The answer came to me when I belatedly remembered having encountered a similar problem a couple months ago on my development server, where I had httpd dynamically loading its binaries, and the problem then turned out to be that I had some modules loading in the wrong order.
Hope this helps someone somewhere down the line! ----- Original Message ----- From: "Per Einar Ellefsen" <[EMAIL PROTECTED]> To: "Noam Solomon" <[EMAIL PROTECTED]> Cc: "Mod-perl list" <[EMAIL PROTECTED]> Sent: Monday, June 17, 2002 6:37 PM Subject: Re: custom directives, again... > At 00:25 18.06.2002, Noam Solomon wrote: > >Thanks -- that got me over one hurdle! Next one: > > > >Syntax error on line 382 of /home/build/httpd/server/./conf/httpd.conf: > >Invalid command 'AddIconByEncoding', perhaps mis-spelled or defined by a > >module not included in the server configuration > >I've replaced the startup.pl call with: > > > > #PerlModule Apache::AutoIndex > > PerlModule Apache::OpenIndex > > PerlModule Apache::Icon > > PerlModule Apache::AuthCookie > >Switching on AutoIndex versus OpenIndex makes no difference. > > > >Any idea what could be going on here? I just tried reinstalling > >Apache::Icon, with > >no improvement. > > Sorry, I'm at a loss here. > > > > >Thanks
