Hi

I'm integrating a C API with my mod_perl application which runs using
Apache::Registry as it is a recent port from a standard CGI environment.

I've got things to work MOST of the time by using the following
configuration;

use strict;
use CGI;
use Crypt::SKey qw(compute_md5);

use Inline ( C=>'/var/www/perl/clipmail.c',
AUTO_INCLUDE=>'#include "/var/www/perl/API.h"',
DIRECTORY => '/var/www/perl/_Inline/',
ENABLE => 'UNTAINT' );

With all my C code in the clipmail.c file and the _Inline directory
configured so apache can read and write to it.

My problem is that if I leave the browser for a while and then come back and
use it again, I get a server 500 error and looking in my error logs I get an
entry as follows NOTE that the _inline directory option listed in the error
IS NOT the same as the one I actually am using which starts with a capital
"I";

>> ModPerl::Registry Invalid value '/var/www/perl/_inline' for config option
DIRECTORY  ... blah compilation aborted.

I don't quite understand this, I am specifying which directory to use - and
it's not that one!! I'm suspecting this is something to do with persistance
and the way mod_perl under Apache::Registry works - I wonder if the error is
cropping up when a new child process is spawned and maybe mod_perl is trying
to re-compile the C code but for some reason is ignoring the config
option???

Any help much appreciated

Regards
Roger Moffatt
UK




Reply via email to