In certain SAV for Linux environments, Talpa may seem to hang during the system start-up, preventing the system from starting.
This is because on system startup, Talpa tries to scan the first file it comes to in each mounted file system to confirm access. In rare cases if a file system has a huge number of empty directories in a directory tree (seen sometimes in Hadoop clusters) then Talpa will appear to hang while it traverses the filesystem looking for a file to scan.
This situation has been addressed in the latest version of Talpa [released January 2020].
On systems where a fixed release of Talpa has been installed, this will first need to be disabled and the latest copy of Talpa binaries collected:
rm /opt/sophos-av/talpa/override/talpa-srcpack.tar.gz rm /opt/sophos-av/talpa/override/build.options /opt/sophos-av/engine/talpa_select select
To prevent Talpa from scanning a given filesystem type on startup an additional option can be set with Talpa 1.25.3 and later. The example below, shows the command to prevent Talpa doing an initial scan of filesystems of a type squashfs:
/opt/sophos-av/bin/savdctl disable echo "no_scan=+squashfs no_scan_on_load=1" > /opt/sophos-av/talpa/override/talpa_vfshook.options /opt/sophos-av/bin/savdctl enable
echo "no_scan=+squashfs no_scan_on_load=1" > /opt/sophos-av/talpa/override/talpa_vfshook.options
If you've spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article. This is invaluable to us to ensure that we continually strive to give our customers the best information possible.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. For technical support post a question to the community. Or click here for new feature/product improvements. Alternatively for paid/licensed products open a support ticket.