Number of files to interrogate

I spoke to Bob (product development for Sophos Anti-Virus for Mac).  It's expected behavior for the scan to do what the video shows.  It's the way the product works as to can only query the operating system and return the number of items Mac OS X calculates - with or without exclusions.

Another thing Bob said is that the scanner can look like it's hung at a particular point, but it's probably just working through a large file or folder.  You should therefore give it time - leave it over night to work through the scan.

I also looking back over past posts and noticed a post where you may be able to see the files being scanned.  Tweaking the original command slightly (changing .txt output to .log) you could run the command below and open the .log file with Console (basically double-click it and it will open in Console) and watch for the point were the scan seems to stall.

1. Open Terminal (search for Terminal from Spotlight).
2. Type (copy and paste this) and press return: sudo sweep / -dn 2> ~/Desktop/manualscan.log
3. Enter your password (won't be displayed as you type) and then press enter.
4. Double-click the .log file that should have been created on your Desktop.
5. Sit back but keep one eye on it.  Also watch the Terminal as files the scanner can't open will be reported in that window and not the log file.
6. If the scan seems to stall be ready to note the file name in TextEdit etc.  The log can move fast but I'm assuming if the scan stalls you'll have a good bit of time to note the file name(s).
   If the scan log never seems to pause it could be due to the activity you're now seeing.  For example the normal program may be doing the same thing but hides the file names being processed and when it gets to a certain folder (with big files or lots of files) it just seems to stall.

Post back how it all goes.

I spoke to Bob (product development for Sophos Anti-Virus for Mac).  It's expected behavior for the scan to do what the video shows.  It's the way the product works as to can only query the operating system and return the number of items Mac OS X calculates - with or without exclusions.

Another thing Bob said is that the scanner can look like it's hung at a particular point, but it's probably just working through a large file or folder.  You should therefore give it time - leave it over night to work through the scan.

I also looking back over past posts and noticed a post where you may be able to see the files being scanned.  Tweaking the original command slightly (changing .txt output to .log) you could run the command below and open the .log file with Console (basically double-click it and it will open in Console) and watch for the point were the scan seems to stall.

1. Open Terminal (search for Terminal from Spotlight).
2. Type (copy and paste this) and press return: sudo sweep / -dn 2> ~/Desktop/manualscan.log
3. Enter your password (won't be displayed as you type) and then press enter.
4. Double-click the .log file that should have been created on your Desktop.
5. Sit back but keep one eye on it.  Also watch the Terminal as files the scanner can't open will be reported in that window and not the log file.
6. If the scan seems to stall be ready to note the file name in TextEdit etc.  The log can move fast but I'm assuming if the scan stalls you'll have a good bit of time to note the file name(s).
   If the scan log never seems to pause it could be due to the activity you're now seeing.  For example the normal program may be doing the same thing but hides the file names being processed and when it gets to a certain folder (with big files or lots of files) it just seems to stall.

Post back how it all goes.