I have no clue what it is
P
I just discovered this in my Login Items. It's "Kind" is "Unknown," and when I right-click on "Reveal in Finder," nothing happens. Besides the obvious date reference (20120126), I haven't a clue what it's all about.
![]() | Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years. Thanks, CNET Support |
I just discovered this in my Login Items. It's "Kind" is "Unknown," and when I right-click on "Reveal in Finder," nothing happens. Besides the obvious date reference (20120126), I haven't a clue what it's all about.
Discussion is locked
I have no clue what it is
P
But let's hope someone has more to offer on this. We used to see folk ask about mystery files a lot more about a decade ago. Today folk seem to not ask. These are usually temp files that some app forgot to clean up.
But worse than that, the user usually has the best shot at knowing where they came from and how to create more.
Bob
Actually, it was<span id="INSERTION_MARKER"> multi-posting.
<span id="INSERTION_MARKER">
<span id="INSERTION_MARKER">
<span id="INSERTION_MARKER">But I do have an idea what it's all about (it occurred to me earlier tonight).
<span>
<span>Last week I did an overdue Software Update. The Update indicated that it found — and deleted — the Flashback trojan. So, I suspect that the "apple-scc-20120126<span>..." file was installed by the trojan. And the "20120126" part suggests that it happened on January 26, prior to my previous (to last week's) Update, which was in February. I have Little Snitch running, so I guess I'm OK...but I don't know for sure. regardless, I'm puzzled why I can't find the apple-scc file on my hard drive.
Looks like a date stamp to me. You would have access to more details since you have the file.
I see others are chiming in with what I think is good advice. Delete and try OpenDNS. Here I use the Google DNS.
Bob
But I can't *find* the file. As far as deleting it, OpenDNS, etc., I don't yet quite understand...
It's a little technical but in my opinion a VERY GOOD IDEA to try other DNS (servers).
It would be strange to write DNS servers since DNS is Domain Name Server followed by the word servers but folk new to all this may give it a pass. Those that get uppity about TCP over IP when I want to shorten the dialogue to just TCP or UDP tend to want this to be exact. We're not using English here.
I see the mystery is still that but the advice looks fine to me.
Bob
You lost me...I haven't a clue how to use OpenDNS; and I don't know what "Google DNS" is.
My difficulty isn't understanding the DNS...it's understanding the purpose of/how to use "OpenDNS.com" and/or "Google DNS."
let's find other than my reasons?
http://ask-leo.com/should_i_use_googles_new_dns_services.html
I read <http://ask-leo.com/should_i_use_googles_new_dns_services.html>, followed the link to Google, and read the "Using Google Public DNS." The instructions appear to outline a not-so-simple effort to change the default DNS server (I imagine it's a similar effort at OpenDNS), but I don't understand what the point is. Why would I want to do change the server?
And I also would *really* like to know why I can't find the "apple-scc-20120126-112417" file.
I did but that does not matter.
But about finding files and folders. Let's talk about today's users. Most are upset when we have to use the command line.
In this case when I see that a file/folder does not show in the GUI I know to open a terminal and look around there.
But here's the deal. This is not something I can teach here. There are plenty of fine web sites with tutorials on the commands CD, LS and such. I can't duplicate such fine work here but it's the next step in finding file or folders that hide from the GUI.
I've also been known to pull the HDD and connect it to some box running LINUX so I can do some forensics. And forensics is even further from something we could discuss here. It's that deep.
Bob