Hi ,

I'm trying to add some features in boinc server, (in linux environment)

but I need all clients information in real time ( if they add in the project already)

for example, after starting the project, I need to know how many clients in my project, are they running the jobs now? , their pc's core numbers....

I think I can get above information in daemons, (maybe in scheduler), any help?

Thanks :)

That's all information you can read from the BOINC database: http://boinc.berkeley.edu/trac/wiki/DataBase

---

but I need all clients information in real time ( if they add in the project already)

for example, after starting the project, I need to know how many clients in my project, are they running the jobs now? , their pc's core numbers....

That is kind of opposed to what BOINC was designed for. The Client will only connect to the server in order to get or report work. It will not tell you what it is doing right now. From more recent Clients you get more information about other projects but that does not tell you what's going on in real time.

The host capabilities are stored in the database and you can deduct the actually used capabilities by taking the individual preferences into account but then again you don't know if the volunteer has other projects running or even local preferences which are not reported to the server.

If you need real time information your app needs to contact your server on it's own. But be warned you may create your own DDoS with that.

Regards
Christian

Some projects use

<next_rpc_delay>x</next_rpc_delay>
In each scheduler reply, tell the clients to do another scheduler RPC after at most X seconds, regardless of whether they need work. This is useful, e.g., to ensure that in-progress jobs can be canceled in a bounded amount of time.

to ensure regular updates.

See Project Options

@Ageless, @ChristianB, @Richard Haselgrove, Thanks,

My purpose is to make the system can submit jobs dynamically by checking client state.
( if all the jobs are completed and there are clients in idle, system will submit new jobs to DB ..... )

So it seems that can't be implemented in BOINC server. (I thought I could utilize some information in BOINC database table "HOST")

@Ageless, @ChristianB, @Richard Haselgrove, Thanks,

My purpose is to make the system can submit jobs dynamically by checking client state.
( if all the jobs are completed and there are clients in idle, system will submit new jobs to DB ..... )

So it seems that can't be implemented in BOINC server. (I thought I could utilize some information in BOINC database table "HOST")

As I said that is the opposite of how BOINC works. You don't know if a host is idle or not. You need to have enough work on the server to fulfill a request by an idle client.

Why can't you pre generate jobs on the server? If you need to wait for other jobs to finish you can trigger this in the assimilator and create a new job.

Can you elaborate on what you really want to achieve and not how you want to achieve it? So what is your problem with how it currently works?

If you need real time information your app needs to contact your server on it's own. But be warned you may create your own DDoS with that.