Daniel Jacobowitz wrote: > > 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. Ah yes, so they are. I still think dlclosing for no good reason sucks though. Alan Burlison
- RE: Why does Apache do this br... Gerald Richter
- RE: Why does Apache do this br... G.W. Haywood
- horrible memory consumption Jason Terry
- Re: horrible memory consumptio... Bill
- Re: horrible memory consumptio... Stas Bekman
- Re: horrible memory consumptio... Bill
- Re: horrible memory consumptio... Cliff Rayman
- Re: horrible memory consumptio... Vivek Khera
- Re: horrible memory consumptio... Doug MacEachern
- Re: Why does Apache do this braind... Daniel Jacobowitz
- Re: Why does Apache do this br... Alan Burlison
- Re: Why does Apache do this braind... Jens-Uwe Mager
- RE: Why does Apache do this braindamaged dlclose/dlopen ... Gerald Richter
- RE: Why does Apache do this braindamaged dlclose/dlopen ... Stephen Anderson
- Re: Why does Apache do this braindamaged dlclose/dl... Gerald Richter
- RE: Why does Apache do this braindamaged dlclose/dlopen ... Stephen Anderson