What would be helpful here would be logging of when a rule *starts*
evaluation. Normally that would be painful, but for tracking a runaway it
would be useful. Perhaps I can code up something to capture that and log
it on a timeout...
Actually what sounds like it would be useful would be knowing the name of
the rule that timed out. I'm presuming when the timeout occurs that there is
still some indication of the current rule being processed so it can be
killed. I'd think that should be enough to backtrack to the rule name. A
modification to the timeout message could display the name of the rule and
even how long it took to that point.
I guess there might be multiple rules running when the timeout occurs and
not know which one really timed out, but that would still be a small number
of rule names.
Loren
