Guest User!

You are not Sophos Staff.

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

    Ruckus,

    I haven't forgotten and appreciate your efforts in trying to get me working again.

    Since receiving this latest instruction, I have tried at least 4 times to run this.

    The first 3 stopped after about 3+hours at the same .dmg file - and never recovered from there.  On the forth attemp, after 86 minutes, the console froze (spinning beachball and even took a couple of minutes to respond to a force quit) but this time at a jpg file.

    As for the terminal session you said for me to keep an eye on, there are loads (too many to easily count) of 'Could not open' lines.  I have attached the text file (converted to jpg) if this could help.  Note: I'm not actually sure if the process is finished but hopefully you will still see the main issues.

    And I will be running the manualscan.log again so if there's anything you can suggest I need to do to help further, then please shout.

    Cheers

    :1014619
Reply
  • 0

    Ruckus,

    I haven't forgotten and appreciate your efforts in trying to get me working again.

    Since receiving this latest instruction, I have tried at least 4 times to run this.

    The first 3 stopped after about 3+hours at the same .dmg file - and never recovered from there.  On the forth attemp, after 86 minutes, the console froze (spinning beachball and even took a couple of minutes to respond to a force quit) but this time at a jpg file.

    As for the terminal session you said for me to keep an eye on, there are loads (too many to easily count) of 'Could not open' lines.  I have attached the text file (converted to jpg) if this could help.  Note: I'm not actually sure if the process is finished but hopefully you will still see the main issues.

    And I will be running the manualscan.log again so if there's anything you can suggest I need to do to help further, then please shout.

    Cheers

    :1014619
Children
No Data