On Sat, 13 Nov 2021, Loren Wilton wrote:
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.
That's what I was thinking when I said "capture and log".
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Running away is the coward's way out of a war;
appeasement is the coward's way into a war. -- Thorax
-----------------------------------------------------------------------
532 days since the first private commercial manned orbital mission (SpaceX)
