is wuprop set up for mult clients running on same host?

let me try to explain, I am not trying to cheat.
I have 22 client running on 4 hosts. I can run 1 wuprop task on each host but that does not pick up the other info from the other clients.
why mult-clients on each host you ask?
each client has one project attached to it.
so running only 1 wuprop task on each physical host does not pick up the information on the other clients..
some of the project only have work every now and then and your just lucky if the host needs work and the project has work at the same time.
by running mult-clients with one attached to the projects that have little work your more likely to pick up work for that project.

I did read somewhere, that the boinc server has a flag that you could set in the server config that would allow mult-clients on one host.

hope this makes sense

http://boinc.berkeley.edu/trac/wiki/ProjectOptions

<multiple_clients_per_host>0|1</multiple_clients_per_host>
Set this if some of your hosts run multiple BOINC clients simultaneously (this is the case on projects that use Condor and/or grid resources, which require each client to use only 1 CPU). If set, the scheduler will skip a check that tries to locate the host based on its IP address.

yep, read it somewhere....

I can now answer my own question. no, wuprop is not. the tasks abort.

What's the reason for using one project per client?
____________
Click here to see My Detailed BOINC Stats

What's the reason for using one project per client?

also on the good side of mult-clients...
say you wish to run 5 projects
4 of the projects play well together.
but one is a pain to run.
lets say this one project has only MT tasks meaning it wants 100% of the host when it runs, has short deadlines, and can take anywhere from a few seconds to over 150 hours to run.
so you put 2 boinc clients on the host and set the 1st one with the 4 good projects on it and the pain project on the 2nd client.
now run both clients on computer preferences.
you let client 1 which has the 4 projects run all day because they don't take over.
and at the time you go to bed client 1 suspends and client 2 unsuspends allowing the bad boy to have 100% of the host and you don't have to deal with the computer becoming nonresponsive. and just before you get up in the morning client 2 suspends and client 1 unsuspends..
in other words you get a lot more control over which projects run and when...

and one more thing.
some of the projects will beat up on your cpu runs hot
and you have to set it to run less than 100% of the time
other projects don't and while running you cpu does not run hot.
so setting up one project per client you can set that client to run at say 80% of time and the others at 100% of the time.

in other words you taylor the options to your host and project.
and could very well save your cpu from burning out...

that is why.
boinc client has never been able to handle more than a few projects attached to it at any given time.
once you attach more than one project to the client you start compounding problems that come up...

Hmm, ok... I guess if that's the way you want to run it. I've never really had any problems running multiple WUs within BOINC, the max I've got is 6 (4 CPU, 1 GPU, 1 NCI) on one host. I manage the heat on systems where that's a problem without any incident.
____________
Click here to see My Detailed BOINC Stats

ok how about this, something like an app_config.xml for wuprop on hosts with multi-clients you can put in the project directory

boinc_data_dir.xml

<boincdatadir>
<dir>C:/programdata/boinc</dir>
<dir>C:/programdata/boinc1</dir>
<dir>C:/programdata/boinc2</dir>
.
.
.
</boincdatadir>

change the app to look in all the listed directory and collect the data...

well, it should be fun to see how fast the admin/dev can program when BOINC goes from
c:/programdata/boinc/client_state.xml
to
c:/programdata/boinc/projects/whatever_project_your_running/project_state.xml

in other words doing away with one client state file and making it one state file for each project, in that project directory.

Any word on this from the Admin, I have the same Problem, I get Credit at the Projects that are running on the 2'nd Client but if I try to run a WuProp Wu on the 2'nd Client it mess's everything up. The Wu will self Abort a lot of times & if it does run to completion it gets marked Invalid which means no Credit for the Hr's run on the 2'nd Client either.

The Project needs to Address this as it's no different than the Guy's running multiple VM's on the same Computer & having them show up as a different Computer. They get Credit for the Wu's & the Hr's on each VM, we should be able to get the same for running Multiple Clients ... IMO


____________
https://stats.free-dc.org/badgesbanner.php?cpid=13a87c3a303bcdca4ba0ed600daebb6b

Thanks I will give it a shot

The app_info.xml is for Linux. Here is a windows version that seems to be working (at least the wus is running). I change the port to 2222 for my host. I will report back after work units from client 1 and client 2 complete and validate.

<app_info>
<app>
<name>data_collect_v4</name>
<user_friendly_name>Data collect version 4</user_friendly_name>
<non_cpu_intensive>0</non_cpu_intensive>
</app>
<file_info>
<name>data_collect_v4_4.13_windows_x86_64__nci.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>data_collect_v4</app_name>
<version_num>413</version_num>
<plan_class>nci</plan_class>
<avg_ncpus>0.01</avg_ncpus>
<max_ncpus>0.01</max_ncpus>
<cmdline>-p 2222</cmdline>
<file_ref>
<file_name>data_collect_v4_4.13_windows_x86_64__nci.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

Where do you put the app file ?
____________
https://stats.free-dc.org/badgesbanner.php?cpid=13a87c3a303bcdca4ba0ed600daebb6b

As far as I can tell it still isn't working, I keep getting this a lot ...

168 WUProp@Home 3/15/2014 4:55:38 PM Result wu_v4_1394230617_123952_0 is no longer usable

54 WUProp@Home 3/15/2014 5:15:41 PM Result wu_v4_1394230617_124240_0 is no longer usable
55 WUProp@Home 3/15/2014 5:15:41 PM Generated new computer cross-project ID: 63ed862e32b5fdafa291b28a6f72d3e5

3087 WUProp@Home 3/15/2014 5:14:31 PM Result wu_v4_1394230617_124222_0 is no longer usable
3088 WUProp@Home 3/15/2014 5:14:31 PM Generated new computer cross-project ID: bf0ef116a3cc5dc5d3cd44cc533002f5

I put the app file in the 2'nd Clients WuProp Directory & then started the Client, they seem to all Abort them selves (Both original Client & 2'nd Client) as no "longer usable anywhere" from a few minutes to an Hour or so ...
____________
https://stats.free-dc.org/badgesbanner.php?cpid=13a87c3a303bcdca4ba0ed600daebb6b

I had to copy the wuprop.boinc-af.org directory to the 2nd client data/projects
directory created the app_info.xml and copy the data_collect_v4_4.13_windows_x86_64__nci.exe to the the wuprop directory
then start the second client then attach to the project
if the app_info.xml and the data_collection exe are not there already it takes an error
at least it worked for me doing that way...
and just to be on the safe side I put an app_info.xml in the 1st client with the default port.

It is working well for me. All 2nd clients are working and validating. Sorry I forgot to report back earlier.

I too had the initial problem where the .exe files disappeared, but I attributed that to stupidly trying the Linux original version of the app_info without looking at it first. I fixed the app_info.xml to the one I posted earlier, copied the exe from the 1st client to the second and it started working.