Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 1338 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

AppleScript to disable on-access scanning

MacMedix

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.
Parents
  • 0

    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
Reply
  • 0

    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
Children
No Data