> Should we be wrapping full rules in alarms (using M::SA::Timeout) to
> prevent this?
You can do this with any rule, a full rule is just easier to mess up.
I'd be concerned of the overhead (and probable timing holes) in wrapping
every rule in an alarm().
As an alternative, how about wrappring the entire rule evaluation process,
less waiting for the net rule returns? That way you could catch any message
that took more than say 10 seconds to run all of the non-net rules.
The complaint position probably would not be as specific, unless the rule
evals were modified to set $global_rule_name before they started doing
anything. I don't nkow that it would even be worth the overhead to do that
though, since this should be a very rare problem.
Loren
