Just observed that after WSAC 8.0.5.87 and Cocktail 7.0.3 has run it's weekly maintenance that WSAC had to run a full scan (ala it's initial scan when installed) after Cocktail finished!
Presumably Cocktail tickled a local WSAC database that should have been hidden?
Early days as I haven't had time to both repeat and also check on my other Mavericks 10.9.2 testbeds yet but thought I'd mention it for any interested Mac user that might have the opportunity to test for themselves (and me of course!) ;)
Yes, insufficient data - far too early to raise a Support Ticket!!
.....and yes I appreciate the Cocktail= "snake oil" argument, and No Cocktail does not have a method of file/directory exclusion (that I've found anyway), and no I haven't raised this with Cocktail Support either...
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.