Thierry Valentin wrote: [...]
PerlChildInitHandler 'sub { require Win32::OLE}'
Hello I've tried this: the startup still fails but this time I have no MS error dialog saying that Apache had a problem Apache "cleanly" refuses to start. But there are still no lines in the error.log
As Jan has answered, the problem is that module is not thread-safe, so my original proposal doesn't work. but see below.
> This raises another question:
> Is there a performance/memory issue regarding preloading a perl module > at startup vs. loading it in ModPerl::Registry perl scripts ?
There certainly is. But each perl interpreter will suffer it only the first time it loads this module, all subsequent requests to the same interpreter will not have any additional overhead.
There is one possible solution that will work for you though. Try to add to startup.pl the following code:
sub My::HappyWorkaround::CLONE {
require Win32::OLE;
}CLONE is a special function which is called when a new interpreter is started. Think of it as ChildInit but for the interpreter.
Did it do the trick?
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
