On Mon, 4 Sep 2000, Warren D. Johnson wrote:
> Thank you for the followup. My original thought was that StatINC reloaded
> modules as appropriate and that each child should share a common cache of
> pre-compiled scripts. Since that is not the case, it makes developing
> larger applications in mod_perl a bit trickier. Trickier because now
> everytime I modify some file that falls under the supervision of StatINC I
> have to do a graceful restart to get all the scripts
> re-synchronized/recompiled/reloaded. Is there any other way around this?
Not really.
My trick is usually to partly getting used to just restart the whole
server (apachectl stop && sleep 2 && apachectl start) and partly to
write as much of the code in a way so it can be tested outside of
the mod_perl environment. That's a good thing to do anyway as it
will allow you to take things down to something much simpler for
testing and debugging. It will also allow you to use the code for
other things.
--
ask bjoern hansen - <http://www.netcetera.dk/~ask/>
more than 70M impressions per day, <http://valueclick.com>
