Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 9288 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SAV on Linux: how to map command line options to scheduled scan parameters

snmdla

When doing interactive scans with savscan (typically /opt/sophos-av/bin/savscan), there are lots of detailed command line options.

In contrast to this, configuring scheduled scans with named scan configuration files, as described in the Sophos Anti-Virus for Linux configuration guide, chapter 12 Appendix: Configuring scheduled scans, has very reduced options.

E.g. savscan has options to control handling of SymLinks (--no-follow-symlinks), or filesystem traversal (--stay-on-filesystem), which we cannot find in the mentioned docs nor in the sample config file /opt/sophos-av/doc/namedscan.example.en



This thread was automatically locked due to age.
Parents
  • 0

    Hi snmdla,

    You are totally right here. The savscan tool is much more powerful and flexible comparing with the "Scheduled Scans" option. This is by design, as "Scheduled Scans" include a simplified number of options to allow easy configuration. You can use savscan with "cron" to specify more advanced scheduled scans.

    Please see the following KB that explain in details the difference between the two:

    https://www.sophos.com/en-us/support/knowledgebase/117346.aspx

    Good day,

    Voicu.

  • 0 in reply to VoicuChirtes

    Voicu, thanks for pointing us to this comparison.

    We prefer the method utilizing savconfig as it is better integrated into the enterprise console.

    Thus, we would welcome if the features of the scheduled (non-cron) method would be furthered with the aim of feature parity.


    Kind Regards, Thomas

  • 0 in reply to snmdla

    Some features we would like to see

    -we do have the parameter "excludeExtension", but we would like to  influence the list of Default extensions that is implicitely active

    -we would like to be able to give the scheduled scan some reduced system priority / i.e. niceness, to limit the performance impact

    -we miss the option to abort a running scheduled scan

    Regards, Thomas

Reply
  • 0 in reply to snmdla

    Some features we would like to see

    -we do have the parameter "excludeExtension", but we would like to  influence the list of Default extensions that is implicitely active

    -we would like to be able to give the scheduled scan some reduced system priority / i.e. niceness, to limit the performance impact

    -we miss the option to abort a running scheduled scan

    Regards, Thomas

Children
Cookie Information Banner