Reply
Occasional Collector
csbc
Posts: 4
Registered: ‎07-06-2012
0

Interrupting 'Scan local drives'

Is there any way this can be done without loosing what has been done if I shut down?

 

Having used Sophos version 8.0.5 for ages I realise I have not done a complete scan before. At present I have 8m files left from over 12m and don't want to start over if it can be helped. It has been running for more than 24 hours and I may have to do a shut down within the next 24 hours when it is not likely to be complete, but I can't see any way to save a partial result.

 

Also, is there any way to make it less greedy? It seems to take all of what I used to call the interrupts and disk accesses which make my Mac incredibly difficult to use. Though I realise that this is a one-off process it is still very tedious!

 

Cheers,

 

Colin

--

'It is a secret in the Oxford sense. You may tell it to only one person at a time.' Lord Franks, letter to Sunday Telegraph, 30th January 1977

Employee
Agile
Posts: 1,191
Registered: ‎11-02-2010
0

Re: Interrupting 'Scan local drives'

If it's being extremely greedy and taking that long to scan, there's an issue, and the scan should be stopped.  You won't be able to save your results, as results may not be the same the next time you scan (while trojans tend to be specific files, any "Anti-Virus" product also protects against file infectors)

 

I'd suggest disconnecting external drives and network shares, and temporarily disabling backups; you should find your full scan takes no more than a few hours in this configuration.  Then you can start adding in your external devices to see if you have a problem.

 

The On Demand scan is supposed to be low footprint and run in the background with minimal interference, allowing you to function normally while the scan takes place.

-
Andrew
Threat Researcher
SophosLabs


For our other self-service and peer-to-peer online support systems:


Occasional Collector
csbc
Posts: 4
Registered: ‎07-06-2012
0

Re: Interrupting 'Scan local drives'

Thanks for that. Next time I'll know better - I supect my problem was having 2x !TB drives on an extended USB run that will have slowed it down.

 

Cheers, Colin