Did you mean global_prefs_override.xml?
Here it is:
- <global_preferences>
<run_on_batteries>0</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<suspend_cpu_usage>25.000000</suspend_cpu_usage>
<start_hour>0.000000</start_hour>
<end_hour>0.000000</end_hour>
<net_start_hour>0.000000</net_start_hour>
<net_end_hour>0.000000</net_end_hour>
<leave_apps_in_memory>0</leave_apps_in_memory>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
<dont_verify_images>0</dont_verify_images>
<work_buf_min_days>0.010000</work_buf_min_days>
<work_buf_additional_days>5.000000</work_buf_additional_days>
<max_ncpus_pct>100.000000</max_ncpus_pct>
<cpu_scheduling_period_minutes>120.000000</cpu_scheduling_period_minutes>
<disk_interval>60.000000</disk_interval>
<disk_max_used_gb>12.000000</disk_max_used_gb>
<disk_max_used_pct>80.000000</disk_max_used_pct>
<disk_min_free_gb>0.050000</disk_min_free_gb>
<vm_max_used_pct>75.000000</vm_max_used_pct>
<ram_max_used_busy_pct>75.000000</ram_max_used_busy_pct>
<ram_max_used_idle_pct>75.000000</ram_max_used_idle_pct>
<max_bytes_sec_up>0.000000</max_bytes_sec_up>
<max_bytes_sec_down>0.000000</max_bytes_sec_down>
<cpu_usage_limit>100.000000</cpu_usage_limit>
<daily_xfer_limit_mb>0.000000</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
</global_preferences>

and here is cc_config.xml

<cc_config>
<log_flags />
- <options>
<client_version_check_url>http://www.worldcommunitygrid.org/download.ph...ent_version_check_url>
<client_download_url>http://www.worldcommunitygrid.org/download.php</client_download_url>
<network_test_url>http://www.ibm.com/</network_test_url>
<start_delay>120</start_delay>
</options>
</cc_config>


I will see what happens regarding running the cache down and setting the buffer to 0.00. It might take a bit, as I don't like aborting the units that are present now.

For the moment your total local overriding prefs amount to buffering 5.01 days.

<work_buf_min_days>0.010000</work_buf_min_days>
<work_buf_additional_days>5.000000</work_buf_additional_days>

At 12 cores, that is 1448 hours of work caching. At 5 hours for a CFSW, that's some 290 tasks.

Once local prefs have been entered, it just takes one field to copy all present web prefs to the local prefs, changing anything on the web except for the sciences is ignored. Hit the clear button in local prefs to restore the use of web preferences.

--//--

It's pleasing to see the new faster CFSW application version 6.11 appearing in downloads. I've just processed the first one in 43 minutes on my i5-750. The estimated completion time on the first few downloads was 4 hours, but the more recent ones are 1 hour.
Now to build up the 5 validated results required to return my CFSW processing to zero redundancy.

Ah, so they're circulating.... good to know.

--//--

Yes, I think your wingman/men have a security software issue. If you had a beta test of this version, then as I understand from Uplinger, the md5sum is the same, just the app name different. Your AV would then be OK with it, at least mine was without protesting for other betas that went to production.

No broken, not stirred, but 6.2.28 is really ready for retirement, whoever still got it. An upgrade from 6.2 to 6.10 is transparent, takes a minute to run and continues where left off, if options are left the same. Changing at the same time from service to user or from user to service... I'd make a data dir backup first and do the upgrade off-line. This allows for testing and copy the data backup in place before allowing server connection again.

--//--