Currently, SUA does not have “scan duration” feature. However, SUA already provides scanner timeout functionality.
The default scanner timeout value is 12 hours (43200 seconds). It can can be changed by Configure Scan Timeout fixlet.
If you have maximum process duration policy in your IT environment, change the default timeout value. The scan result will be logged in the Software Scan Status analysis, where timeout scan status is returned by code 29.
I know the Scan Timeout value but our client wants to know the exact time that the software scan runs.
We have had problems with running scans on systems and although we now have limited CPU consumption by wscansw process but the client wants to have completely controlled the runtimes of the scans.
Please, ask to comment and vote for given RFE if the feature is highly required.
Temporarily, please try monitoring the last modification time of following files:
start time of all scans:
…/BESClient/LMT/CIT/last_sw_scan_attempt.info
end time of catalog-based scanner:
…/BESClient/LMT/CIT/last_catalog_scan_success.info
end time of file system scanner:
…/BESClient/LMT/CIT/last_file_scan_success.info
end time of sw identification tags scanner:
…/BESClient/LMT/CIT/last_iso_scan_success.info
Scans are run in sequence, so to get duration you need to subtract:
(end time of catalog-based scanner) - (start time of all scans) = duration of catalog-based scanner
(end time of file system scanner) - (end time of catalog-based scanner) = duration of file system scanner
(end time of sw identification tags scanner) - (end time of file system scanner) = duration of sw identification tags scanner