> Probably the biggest reason for dlopen/dlclose on a restart is that the
> list of modules in the config file can change on a restart.  The reason
> for the reload on startup has something to do with parsing the config
> file in the parent and child; it was never adequately explained to me.
>
> The trick would be getting it not to do this without busting up the
> module API, which I can actually think of a few ways to do, and in a
> way that the Apache Group didn't rigorously object to :)
>

Do you know, would it be possible to catch the dlclose inside mod_perl and
unload (dlclose) all external libaries that Perl has loaded so far? The
problem is, that these libraries will persist between such an dlclose/dlopen
and afterward don't get proberly initialised, so some of the code really
points to data from the old Perl interpreter, which causes strange
behaviour.

Gerald




-------------------------------------------------------------
Gerald Richter    ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting

Post:       Tulpenstrasse 5         D-55276 Dienheim b. Mainz
E-Mail:     [EMAIL PROTECTED]         Voice:    +49 6133 925151
WWW:        http://www.ecos.de      Fax:      +49 6133 925152
-------------------------------------------------------------

Reply via email to