Guest User!

You are not Sophos Staff.

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

Sophos AV Hangs

Lankidden

Hi Guys,

Along with many others, have now installed Sophos on MBP OSX 10.6.4. HD 350Gb, 250GB available. Initial scan displayed approx 500k files needed scanning, which went smoothly in background, until hanging at around 75k. I cancelled scan after around twenty minutes, and restarted scan some time later. Again the scan hung at around 75k, but this time I left it to sulk on it's own. Some two hours or so later an OS window came up saying that my launch disc was now full, and files needed to be deleted. Initially thinking this must be referring to some scratch disc I was not too concerned, but then I checked the available  space on the HD, and indeed available space was a big fat ZERO. After returning from a rapid visit to the facilities ( ! ! ! ! !) I rebooted, and was very relieved to see that available space had reverted to around 250Gb, so presumably all's well that ends well.

So, having made sure that both my Time Machine & external HD Back-ups are up to date, I am somewhat loath to go for a third scan.

Any suggestions as to what might be my problem, or is it just that Sophos, perish the thought, sadly couldn't recognise some sort of problem, and fell over in the attempt?

All thoughts and advice gratefully received.

Lankidden

Oxford UK

:1000215


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

    Thanks for the feedback.  The issue is that when the scanner is "stalled" it provides no feedback that it is in fact still working, but scanning inside an archive -- other than the progress throbber still throbbing.  If you re-check search in archives and compressed files, you'll find that when you hit that stalled patch, it will appear to be doing nothing for a while, during which time it is unpacking and scanning a large archive.  When complete, the progress bar will continue to move.

    The alias issue shouldn't be an issue, as the symlink files themselves are scanned, not the file they link to.  These days, aliases are really UNIX symbolic links.

    :1004143
Reply
  • 0

    Thanks for the feedback.  The issue is that when the scanner is "stalled" it provides no feedback that it is in fact still working, but scanning inside an archive -- other than the progress throbber still throbbing.  If you re-check search in archives and compressed files, you'll find that when you hit that stalled patch, it will appear to be doing nothing for a while, during which time it is unpacking and scanning a large archive.  When complete, the progress bar will continue to move.

    The alias issue shouldn't be an issue, as the symlink files themselves are scanned, not the file they link to.  These days, aliases are really UNIX symbolic links.

    :1004143
Children
No Data