I solved the prob I had some time ago (see below) by adding "PerlModule
BerkeleyDB" to the httpd.conf:
...
# Load Apache::Registry
PerlModule Apache::Registry
# Load Berkeley DB
PerlModule BerkeleyDB
...
It runs fine now.
But I'm not exactly sure what went wrong in the old situation
On Fri, 2005-04-15 at 23:46 +0200, Rick Jansen wrote:
> No, that should not be the case, I think. The env-open and the "new
> BerkeleyDB::Hash" are actually called in the run routine, like below,
> simplified.
What you have below will call run() during startup. All the code
outside of subs in yo
Perrin Harkins zee op 15/4/05 17:19:
> Rick Jansen wrote:
>> # crashes:
>> my $DB_Object = new BerkeleyDB::Hash
>> -Filename => $DB,
>>-Env => $Env,
>> -Flags => DB_RDONLY ...
>
> The rest of the flags here may be relevant.
Rick Jansen wrote:
# crashes:
my $DB_Object = new BerkeleyDB::Hash
-Filename => $DB,
-Env => $Env,
-Flags => DB_RDONLY ...
The rest of the flags here may be relevant.
To avoid name collisions the application is split in a ma
I'm converting an existing CGI-script that uses Berkely DB with CDB to a
mod_perl version, and I'm running into a problem. The first run works
fine, but the second hit causes a "child pid ... exit signal
Segmentation fault (11)" in the following line, UNLESS I close the
environment after each run,
