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

AppleScript to disable on-access scanning

HI,

It was mentioned that Sophos on-access scanning can be controlled via AppleScript. Could you please provide an example AppleScript to disable and to re-enable Sophos for Mac on-access scanning?

I need to disable on-access scanning while a Mac OS X backup software ( SuperDuper ) runs because when Sophos detects a virus, it locks access to the file, the backup app retries, then aborts the whole backup. So the backups are not completing. It is more important to us to have a good backup, than to not backup infected files. We can run an AppleScript before & after the backup, so disabling on-access scanning seems like a good work around.

Thanks,

 Dave

:41845


This thread was automatically locked due to age.
  • Anybody? I can't be the only person in the world with this problem. Has nobody solved it? it has been about 2 months with no reply. Is there a better place to ask this question?

    :43755
  • As I hope you can imagine it's tricky to give out such a script (if it exists) on a freely accessible forum.

    The better way to do it is to open a ticket with Technical Support so we can understand the issue better and possibly resolve the underlying problem - rather than workaround it.  Of course opening a ticket is based on you using the paid for version of Sophos Anti-Virus for Mac (not the free one) and therefore having a license and entitled to contact our support team.  Have you bought the product or is this the free Mac Home Edition?

    FYI:  The home edition is exclusively supported on Sophos FreeTalk (not this forum).  There are Sophos Mac developers on that forum, so there may be more help available.

    :43765
  • I don't want to repeat what ruckus just said above (provider of wireless products by any chance? :smileywink: ) but is this a managed or unmanaged version?  If it's the managed one, the ideal solution would be to configure a policy to move any infected files into a quarantine area which would then allow your backups to proceed.  If you really wanted to, you could also include the quarantine area in your backups and have it excluded from on-access scanning.  I'm not sure what functionality exists in the non-managed version, but I'm assuming you'll still be able to quarantine infected files to keep them out of the way of the backup jobs.

    I also assume setting the backup software to continue on errors isn't an option?

    :43845