Jord(Ageless) suggested I move some of my WU's into a BOINC (those that aren't VBox themselves) virtual machine because the client doesn't handled app_config.xml limits on WU properly.

Instead of using a virtual machine I split BOINC into two clients running 4 and 2 cores on a 6 core machine in order to solve the work fetch issues of idle cores from high resource projects, without work, on that machine (it works really well now) but the WUProp monitoring one of the clients (I think the 4 core doing the most work) gives 90% validation errors even tho there are 30 minute WU's being done.



I am not sure which of these is the 2 core or the 4 core because the two clients are now nameless. Not sure how to fix that. So the two descriptions might actually be swapped.

installed directory client doing 2 cores and GPU
2nd client running 4 cores copied to a new directory running boinc.exe on a new port and manually connecting to it from a second boincmgr.exe process

If I understand correctly WUProp telnets into the client through the standard port instead of actually monitoring the RAM of the machine. Since the second client is moved to port 9000, is this the problem? Can I tell WUProp the new port number?

This old forum post may have some information in it that could help you.

http://wuprop.boinc-af.org/forum_thread.php?id=253#2021

It concerns multi clients

Hope it helps and everyone have a good New Year.

Conan

---

Thanks a lot!

Here's the solution from that post (I don't understand why quote or code tags are eliminating white characters on these forums):

<app_config>
<app_version>
<app_name>data_collect_v4</app_name>
<plan_class>nci</plan_class>
<avg_ncpus>0.01</avg_ncpus>
<cmdline>-p xxxx</cmdline>
</app_version>
</app_config>

Where xxxx = your client's non-standard port other than 31416.