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

Sophos Linux don't accept the configuration " UpdatePeriodMinutes "

Hello


After recent update Sophos Free Linux don't accept more the configuration when I put in " UpdatePeriodMinutes " (#/opt/sophos-av/bin/savconfig UpdatePeriodMinutes 1440 ) 1440 minutes ( 24 hours ).

Now it update every 4 hours.


Any solution ?


Thanks



This thread was automatically locked due to age.
Parents Reply
  • Your method disables all updating.

     

    As I said before the product updates:

    a) During boot - if on-access enabled, talpa enabled, and no TBP matching the current kernel.

    b) 5-10 minutes after savd starts.

    c) UpdatePeriodMinutes after the last scheduled update.

     

     

    b & c are controlled by the EnableAutoUpdating option.

     

    Machines need to update every ~ 4 hours to get new protection data, otherwise protection is compromised.

     

Children
  •  

     

    Hello !!!

     

    I now configured in the root terminal:

    #/opt/sophos-av/bin/savconfig set EnableAutoUpdating false

     

    After I verified with:

    #/opt/sophos-av/bin/savconfig query EnableAutoUpdating

    And it returned: " false " !!!

     

    Now I manual updated every day with:

    #/opt/sophos-av/bin/savupdate

     

    Thanks Douglas !!!

     

    Happy new year for you and your team from here Brazil !!!

     

    by !!!

  • Hello,

    For me it is as Douglas described

     

    root@debian:~# /opt/sophos-av/bin/savconfig query EnableAutoUpdating
    TRUE
    root@debian:~# /opt/sophos-av/bin/savconfig query UpdatePeriodMinutes
    1440
    root@debian:~# systemctl status sav-protect
    ● sav-protect.service - "Sophos Anti-Virus daemon"
    Loaded: loaded (/lib/systemd/system/sav-protect.service; disabled; vendor preset: enabled)
    Active: active (running) since Tue 2019-01-08 11:25:18 CET; 37min ago
    Docs: man:sav-protect
    Process: 16120 ExecStartPre=/opt/sophos-av/engine/.sav-protect.systemd.prestart.sh (code=exited, status=0/SUCCESS)
    Process: 16141 ExecStartPost=/opt/sophos-av/engine/.sav-protect.systemd.poststart.sh (code=exited, status=0/SUCCESS)
    Main PID: 16140 (savd)
    Tasks: 29 (limit: 4297)
    Memory: 520.1M
    CGroup: /system.slice/sav-protect.service
    ├─16140 savd etc/savd.cfg
    └─16633 savscand --incident=unix://tmp/incident --namedscan=unix://root@tmp/namedscansprocessor.1 --ondemandcontro

    janv. 08 11:25:14 debian savd[16140]: savd.daemon: ONACCESS-ENABLED fanotify
    janv. 08 11:25:18 debian systemd[1]: Started "Sophos Anti-Virus daemon".
    janv. 08 11:32:56 debian savd[16140]: update.updated: UPDATING_FROM_VERSION 9.15.1 3.74.2 5.58
    janv. 08 11:32:56 debian savd[16140]: update.updated: Updating Sophos Anti-Virus....
    Updating SAVScan on-demand scanner
    Updating Virus Engine and Data
    Updating Manifest
    Update completed.
    janv. 08 11:32:56 debian savd[16140]: update.updated: UPDATED_TO_VERSION 9.15.1 3.74.2 5.58
    janv. 08 11:32:56 debian savd[16140]: update.updated: SUCCESSFULLY_UPDATED_FROM sdds:SOPHOS
    janv. 08 11:37:05 debian savd[16140]: savscand.control.log: EXTRA-SCANNER-STARTED
    janv. 08 11:37:11 debian savd[16140]: savscand.control.log: EXTRA-SCANNER-STOPPED
    janv. 08 11:52:57 debian savd[16140]: savscand.control.log: EXTRA-SCANNER-STARTED
    janv. 08 11:53:03 debian savd[16140]: savscand.control.log: EXTRA-SCANNER-STOPPED
    root@debian:~#

     

    Only one update after Sophos started.

    Everything goes fine