Linux Security 64 servers display real-time scanning status as "Disabled" in Policy Manager console status page. Policy for these servers is set to real time scanning as "on" and users are not allowed to change this setting.
Why does the status show real-time scanning as disabled even if it should be enabled?
With the latest release of Linux Security 64, it checks now if the real time scanning is configured to scan anything.
It is a product design that there is a need to add the files and folders to scan after the product installation in case of real time scanning.
By default nothing is scanned, so you need to add some paths (for example, root directory of "/" for scanning all files) to the "Files and folders to scan" configuration in order to make the real time scan working.
For safety reasons, we do not start scanning things by default but it is up to the user to configure the real time scanning as they see fit.
This behavior is totally different from Windows product and even the old unsupported Linux Security 11.xx product, where all files are scanned by default after the installation.
If you have not configured it yet, you could perform the following steps to change the configuration for the real time scanning and distribute the policy.
- Login to Policy Manager Console
- Select the Linux Security 64 host on the domain tree
- Go to "Settings" tab > "Linux" > "Real-time scanning"
- Enter root directory (/) at "Files and folders to scan" setting
- Click on "Distribute Policies" button at the top left corner of Policy Manager Console screen
- Click on "Distribute" button to proceed with the policy distribution
- Check if the correct status is shown now
- Open the Terminal
- Run the following command as root user
- Check the diagnostic file (fsdiag-linuxsecurity-yyyymmddxxxxxx.tar.gz) in the "/var/opt/f-secure/linuxsecurity" directory
Article no: 000039496