07-25-2011 12:33 PM
Specimen wrote:@lyoko37 to be fair, Apple already seeded 10.7.2 to developers to test iCloud, that probably implies a 10.7.1 in the next weeks.
Besides lion is so new that there are no threats yet (???????!!!!)
At least lets hope...
07-26-2011 04:20 PM - edited 07-26-2011 04:21 PM
Can anyone who is experiencing the issue with InterCheck and Time Machine confirm whether or not their On-access scanning preferences are configured to scan "Files on network volumes"? And if it is enabled, does disabling it allow the TM backup to complete?
Thanks,
Alex
07-27-2011 09:56 AM
I had external drives included. So TM writings to that disk would be checked by Sophos immediately. I will give it a try with external discs excluded. However should I also exclude my iDisc? I can see it in the preferences as oject to be excluded, but if it was also checked before I excluded it, it could too bring trouble.
07-27-2011 09:59 AM
Definitely worth testing; this doesn't seem to show up in all configurations, so the more edge cases we can explore, the better.
07-28-2011 02:32 AM
So far so good...
I tested it for a while and the result is that I will keep it working like this. Which means:
I disabled all the external discs from scanning. I only allowed one external partition to be scanned but NOT time Machine.
My mac seems to stay stable and it seems no more maxing out of CPU, is happening. I will come back to report if it stays this way or if it goes crazy again.
07-28-2011 09:00 AM
lemon wrote:So far so good...
I tested it for a while and the result is that I will keep it working like this. Which means:
I disabled all the external discs from scanning. I only allowed one external partition to be scanned but NOT time Machine.
My mac seems to stay stable and it seems no more maxing out of CPU, is happening. I will come back to report if it stays this way or if it goes crazy again.
Excellent news! So you're saying that you are and were not using network shares, but were scanning all locally attached media, and that excluding your Time Machine drive fixed the CPU error?
07-29-2011 04:50 AM
I did use a network share, that I now excluded. I did also use Time Machine,which I now excluded. The only spike I saw so far was when Sophos updated from 7.3.1 to 7.3.2 but only DURING the update. After that it returned to normal behavior. I have one local disc attached that is included in the Sophos scan. But it is not giving any problems anymore.
08-05-2011 01:46 AM - edited 08-05-2011 01:47 AM
Yesterday I did a re-install of 10.7. Due to widespread reports of computers crashing for no obvious reasons. (see http://goo.gl/ewcLd )
I thought maybe a re-install could help. After the re-install the settings of Sophos remained the same. Yet Sophos, Time Machine and Spotlight were each fighting for the CPU. So after all I think the settings of Sophos do not matter so much. I had do uninstall Sophos, stop Time Machine and wait for Spotlight to work itself through all the files. When Spotlight calmed down I enabled Time Machine. It took an awful lot of time and processor attention to complete it's 'first' backup. When TM was finished I re-installed Sophos again. Maybe it would have been enough to disable it. But after doing that I still saw intercheck going nuts on the processor. So I removed Sophos temporarily.
Now everything seems to be normal. I don't know if my black-screen bug is gone..........
But maybe you should advice ppl to disable Sophos when they install new system software.
12-28-2011 01:18 PM
Immediately noticed a problem with Intercheck, specifically it takes 115MB memory which forces paging out . Intercheck utilizes the largest chunck of memory and holds it even when it is not running. Would reccomend SAV 7.3.1 only with a memory upgrade.