On Tue, Jan 18, 2000 at 08:03:42PM +0000, Alan Burlison wrote:
> The current fix is to forcibly unload the perl XS modules during the
> unload. However, on reflection I'm not at all sure this is the correct
> thing to do. Although you can unload the .so component of a perl
> module, you can't unload the .pm component, so just removing the .so
> part as in the current workaround is suspect at least.
Remember - mod_perl is being unloaded. Perl going away. At this point
perl_destruct/perl_free have already been called, and thus the .pm
components are effectively unloaded.
> I think the correct fix is for the Apache core to avoid dlclosing
> anything it has dlopened in the first place. If new modules have been
> added to the config files, they should be dlopened, but any old ones
> should *not* be dlclosed, EVEN IF THEY ARE NO LONGER IN THE CONFIG
> FILE!!!
>
> I firmly believe this needs fixing in the Apache core, not by hacking
> around it in mod_perl.
>
> Alan Burlison
>
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| [EMAIL PROTECTED] | | [EMAIL PROTECTED] |
\--------------------------------/ \--------------------------------/
