david c4b27a31b4 Don't ignore host state changes when the change is to the state "unknown". This ...

happens when a host was scanned in the A scan but wasn't scanned in the B scan.
I previously had it ignore such changes using the logic that the diff should be
like scan aggregation: no new information means no state change. But I think
it's more useful to see those changes in which hosts were scanned.

This is analogous to r10263, which did the same thing for port state changes.

2009-01-20 21:02:15 +00:00

19 KiB

Executable File

Raw Blame History

View Raw