A quick look at the code makes me believe it is a bug. looking at GIT Master,
in client/log_flags.cpp, CC_CONFIG::parse_options_client() has on lines 414-415:
if (xp.parse_int("ignore_intel_dev", n)) {
ignore_gpu_instance[PROC_TYPE_INTEL_GPU].push_back(n);
but in lib/cc_config.cpp, CC_CONFIG::write() has on lines 626-630:
for (i=0; i<ignore_gpu_instance[PROC_TYPE_INTEL_GPU].size(); ++i) {
out.printf(
" <ignore_intel_gpu_dev>%d</ignore_intel_gpu_dev>\n",
ignore_gpu_instance[PROC_TYPE_INTEL_GPU][i]
);
So it is expecting the option as <ignore_intel_dev>, but when it updates the
file it writes the option as <ignore_intel_gpu_dev>.
Cheers,
--Charlie
On Aug 23, 2017, at 6:58 PM, clharding...@verizon.net wrote:
> I don't know if this is an actual bug or not, but it is something that has
> been happening for a couple of years through various versions of the BOINC
> manager/client. If one explicitly ignores the Intel iGPU via the
> cc_config.xml (<ignore_intel_dev>0</ignore_intel_dev>), said option will
> disappear from the file after several days. I haven't been able to pin down
> exactly how long the option exists in the file prior to removal. The option
> last appeared in the event log on 19 Aug. I was in the event log this
> evening to look at something else and noticed that the option is no longer
> being logged. I've reinserted the option and will keep a closer eye on it.
>
> Even though the Intel iGPU is ignored implicitly via the global preferences,
> I choose to also have it explicitly in the cc_config.xml. My question is
> this a bug and should this be investigated?
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
