We had this same problem when we initially installed Google Desktop. The reason is because there are lots of files that are created and removed when Condor jobs run on a machine which triggers additional search indexing. You don't need your search engine indexing these files. Our solution was to exclude C:\condor from the search. ~B From: Michael O'Donnell <odonnellm@xxxxxxxx> Reply-To: Condor-Users Mail List <condor-users@xxxxxxxxxxx> Date: Mon, 25 Jul 2011 11:21:22 -0600 To: <condor-users@xxxxxxxxxxx> Subject: [Condor-users] Condor_master and Search Indexer Windows service Has anyone using Condor and Windows systems seen problems with the Windows search index and condor master jointly consuming a machines CPU? Between these two services 100% of the machine's CPU is taken. My guess is that either log files or something is causing a positivefeedback loop. |