Have you tried Apache::StatINC? Actually, is that available for Apache2?
We've also had problems with Apache::Reload here but we're putting that down to
using RHEL mod_perl 1.99 ;) Am waiting to get the latest MP2 installed and
hopefully it'll help sort the problems out.
But I agreee with Perrin, if you're seeing the problems after bouncing the
server, you're either looking at the wrong code ........... or you're sitting
at s.o else's desk ;)
-Ants
Perrin Harkins <[EMAIL PROTECTED]> wrote: On 2/20/07, [EMAIL PROTECTED] wrote:
> Gotcha. However, restarting apache doesn't seem to do the trick. Is it
> maybe unrelated to Apache2::Reload?
If stopping and starting apache doesn't pick up your changes,
something is seriously wrong. You might be looking at the wrong
apache or updating the wrong files. Note that I mean "apachectl stop"
and "apachectl start".
> I've noticed that if I go through and make a LOT of changes (commenting stuff
> out), then go back and undo my changes to get me back to square one, that
> sometimes fixes it. However, 5 - 10 minutes per change really gets old.
10 minutes? You should never have to put up with that. That reminds
me of working on IBM's WebSphere tools. Your server should only take
a couple of seconds to restart and should pick up all of your changed
perl files.
- Perrin
---------------------------------
What kind of emailer are you? Find out today - get a free analysis of your
email personality. Take the quiz at the Yahoo! Mail Championship.
