On Wed, 2003-09-17 at 12:44, Tom Schindl wrote: 
> Hi,
> 
> are you sure it works this way. You should add your /home/arne/scripts
> to @INC, I'm afraid that your usage of PerlRequire is not appropiate,
> because it does not modify the include path.

> On Wed, 2003-09-17 at 12:34, Robert Ferney wrote:
> One thing that people (myself specificaly) sometimes forget to check is
> the permissions in the directories involved.
> Since Apache is most likely running as some user other than 'arne'
> chances are that the default permissions on the directory /home/arne
> won't allow the apache user to get any of the modules in that path..

Turns out it's a combination of both Tom and Robert's suggestion.
PerlRequire worked fine for adding direct handlers from
/home/arne/scripts, such that:

  PerlRequire /home/arne/scripts/XML2HTML.pm
  PerlTransHandler Apache::XML2HTML

worked fine, because XML2HTML was loaded at apache startup and hence was
loaded by root before it spawned of the children as the apache user.

The AxKit directive, on the other hand got invoked at runtime and apache
did not have access into /home/arne/scripts, so it failed on

  AxAddDynamicProcessor Processors

when it tried to require the lib whether or not the /home/arne/scripts
was in @INC. Funny thing is that PerlRequire should have pulled it into
memory already, since it did for Apache::XML2HTML, alleviating the
permissions problem, but i suppose, a eval'ed require does always check
for the file even if its contents are in memory.

All fine now. Now with the combination of my PerlTransHandler and my
AxAddDynamicProcessor, i'm getting exactly the behavior i wanted.

Thanks everyone,
arne


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to