Removing com.google.keystone.daemon

WZZZ & roam...

Thank you for your continued interest in helping me to solve my problem. As to whether it is truly a problem, or merely an annoyance, I'd have to confess to the latter. I'm not entirely certain that the issue at hand is actually affecting the performance of my computer. Rather it would seem that it is simply leeching some of my bandwidth sending an update query literally every 10 seconds. Nevertheless, I appreciate your willingness to lend a hand.

In addressing your most recent theories and suggestions, here's where I stand. I've performed as thorough of a HD search for Google related items as I believe is humanly possible. After running Monitor activities for 'All Processes,' it revealed no Google activity leading me to believe we are on the right track. Exploring your additional suggestions for possible hiding places, I'm happy to report that most all were dead ends, although I did find a few other small and seemingly innocuous Google colonies elsewhere and have confidently eradicated them. There are 2 exceptions however: The previously mentioned 'Gild.frameworks' and 'GoogleML.bundle,' neither of which do I have any idea of their intent or function. Both are the only Google folders remaining on my HD. I am prepared to eliminate them as well (to create a clean sweep), but I'd really like to know their purpose before doing so. Any ideas?

At this point, and in light of my report, you're then probably wondering whether or not my logs still show any signs of 'com.google.keystone.daemon' gumming up the works. Honestly, I'm almost afraid to look for fear that if in fact it is still present, I may just chuck my laptop out the window in frustration.

So, should I opt to rid my HD of the last 2 remaining vestiges of Google, I will then reboot, perform a maintenance check and gauge the outcome of our fishing expedition.

I await your suspicions surrounding the importance of 'Gild.frameworks' and 'GoogleML.bundle.'

Regards.

WZZZ...

In an earlier comment, roam seem to feel assured that the Gild.framework and its associated driver should be 'unloaded' rather than 'trashed.' See below:

com.google.driver.Gild' does ot exist.

It does exist. You have already proved that. But it is not something to be found in Finder. It is a process that is loaded in the kernel.

I said "This driver sits at a fundamental level"

It does not have to be removed, it has to be unloaded. using the correct command in Terminal.

roam & WZZZ...

Problem solved!! I held off on trashing the last 2 items (mentioned above) solely out of trepidation, assuming that if all else failed I push the button. I then tempted fate by running one last maintenance check before pulling the trigger. Surprisingly, the 'google.keystome.daemon' that's been filling up my system logs with calls every 10 seconds has been terminated, apparently after the last batch of Google related files that I found were trashed. Among them was Google Talk, the last item that I had systematically eliminated. Although I've never downloaded Google Talk )as I have no use for such services), components of it somehow managed to find their way onto my computer. Perhaps it's a part of their Google+ social networking garbage, although again, I've never signed up for it, nor have I created an account.

Regardless, the culprit appears to be gone (at least for now) unless it somehow manages to stealthily penetrate my system once again.

I sincerely thank you both for your input and for your salient suggestions in walking me through this. My regards to you both.

Oh yeah, just to clarify --- the Google Talk file that I disposed of was NOT an application. All (3) of my former Google apps were among the first of items to be deleted. If memory serves, I found the folder in either my Application Support folder or Input Managers. Although I don't recall specifically what sort of files were contained within, I simply knew that I had no use for anything like Google Talk and chucked it. It may have merely been an element that was present and ready to be utilized should I ever wish to put Google Talk in place. I hope that's of help to you, and anyone else troubleshooting this same problem.