Nothing in Learning. Just went to 5.4.3 this morning (from 5.4.2),
netscan still sucks the whole CPU, haven't caught reportd doing it but I
may not have been looking when it did.
We've found other things that drive the CPU nuts, one is VPN'ing out
with SSLVPN back into the same subnet, but that makes sslvpnd go high
CPU, not reportd and not netscan. And a simple rule blocks the SSLVPN
loopback. Wish I had an answer to the rep...
Same thing here, on 5.4.2 on a 90D. Also see "netscan" jumping up as
well. If there were a way to make "reportd" and "netscan" into "low
priority" (shows as "N" on diag sys top) I wouldn't have a problem, but
as it is "reportd" grabs so many CPU cycl...
You are leaving our website
You are leaving our site and we cannot be held responsible for the content of external websites
