Setting the Maximum Run Time for Scans

By default, a sensor can run a scan for an indefinite period of time, thus preventing it from running other scans. You can limit the amount of time scans can run on sensors by setting the scan_timeout option (in minutes) for a given job, for a given sensor, or globally for all sensors.

Precedence in Timeout Settings

The following rules of precedence apply to timeout settings:

Job timeout settings override any sensor-specific or global timeout settings.

Sensor timeout configured on the command line overrides a global timeout setting.

Configuring Maximum Run Time for a Specific Job

To configure the maximum run time of one minute for a given job, run the following:

scancentral -url <controller_url> start -package <path> --scan-time-out 1

To configure the maximum run time of two minutes for a given sensor, run the following:

scancentral -url <controller_url> worker --scan-time-out 2

Configuring Maximum Run Time for All Sensors

To configure the maximum run time for all sensors:

Navigate to the <controller_dir>/tomcat/webapps/scancentral-ctrl/WEB-INF/classes directory, and open the config.properties file in a text editor.
Set the scan_timeout property to the maximum number of minutes for scans to run on sensors.
Save and close the config.properties file.