Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 6 subscribers
  • Views 23566 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

Number of files to interrogate

RCully

When I look in finder, it indicates that my iMac as circa 950,000 files.

When Sophos starts scanning, it shows that it has calculated circa 2,100,000 files.

I have excluded any external drives so can anyone please tell me why this scan number is so high?

By the way, I have Mavericks running and also the latest version of Sophos.

Cheers

:1014301


This thread was automatically locked due to age.
Parents
  • 0

    FYI:  Rather than uninstalling and reinstalling try forcing the 'SophosAVAgent' process to quit from Activity Monitor (if the scan locks up).

    2013-11-15_16-39-13.png

    So the issues are:

    1. The item count shown at the start of the scan would indicate that the Time Machine volume is being included in the scan.
    2. The scan hangs part way through and this may be due to the exclusion not being applied in point 1.

    For number one I've videoed below what I've seen.  It seems the behavior is that the scan does an item count of all drives and that is the number you see when the scan starts.  However the scan doesn't actually scan the drive being excluded and completes earlier - in never counts all the way down to zero items.

    Have a watch of the video below to see if that makes sense to you and it should answer point 1.  Obviously point 2 still needs to be addressed - I'll ask Bob to comment - but chances are it's not to do with the Time Machine being scanned, maybe it's a file on your main hard drive.

    :1014519
Reply
  • 0

    FYI:  Rather than uninstalling and reinstalling try forcing the 'SophosAVAgent' process to quit from Activity Monitor (if the scan locks up).

    2013-11-15_16-39-13.png

    So the issues are:

    1. The item count shown at the start of the scan would indicate that the Time Machine volume is being included in the scan.
    2. The scan hangs part way through and this may be due to the exclusion not being applied in point 1.

    For number one I've videoed below what I've seen.  It seems the behavior is that the scan does an item count of all drives and that is the number you see when the scan starts.  However the scan doesn't actually scan the drive being excluded and completes earlier - in never counts all the way down to zero items.

    Have a watch of the video below to see if that makes sense to you and it should answer point 1.  Obviously point 2 still needs to be addressed - I'll ask Bob to comment - but chances are it's not to do with the Time Machine being scanned, maybe it's a file on your main hard drive.

    :1014519
Children
No Data