On 8/12/05, Earl Hood <earl(_at_)earlhood(_dot_)com> wrote:
On August 12, 2005 at 15:49, East Coast Coder wrote:
I should note that I use a require $ENV{...} in the callbacks, to
allow easy change to a config file - but I've been doing this for a
while, with no problems. If the envar isn't set, -c fails.
Require caches what is loads, so if the value of $ENV{...} does
not change (i.e. it resolves to the same file), perl does not
reparse the file.
Right - I just use this to allow me to change configuration files
without having to do a SCm check out / edit / check in - just change
the envariable before running.
The latest version v2.6.15, so you may want to try it just to
see if anything changes.
Note, v2.6.12 did have a modification to how some API callbacks
were handled. You should check the release notes and then your
code to see if this change affected you.
If the problem is still present, then you may have to debug things to
figure things out, including debugging mhonarc code, concentrating
on parts that tell mhonarc to stop processing a message. My guess,
mhonarc is getting a stop indication from somewhere. You can either
run things under the perl debugger or just add some temporary print
statements to see where mhonarc decides to skip further processing.
Okay, will do.
--ewh
---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHONARC-DEV
---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHONARC-DEV
