https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #42 from Kristof Provost ---
(In reply to hlh from comment #40)
> dtrace: processing aborted: Abort due to systemic unresponsiveness
You'd have to talk to a dtrace specialist about that. I'm not sure what
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #41 from Kristof Provost ---
(In reply to hlh from comment #38)
> Why ARC at 233% and 1727Mb wired?
The ARC now keeps compressed data, so you can fit more in memory. I suspect
that's a result of that.
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #40 from h...@restart.be ---
(In reply to hlh from comment #33)
When I run the dtrace in batch, it end freqently with:
dtrace: script './pf.dtrace2' matched 2 probes
dtrace: buffer size lowered to 2m
dtrace: processing
On Fri, 20 Oct 2017, Max wrote:
set skip on lo
(orĀ set skip on lo0)
Already have it...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
___
freebsd-pf@freebsd.org mailing list