This approach will work; I'll check in something equivalent.
Thanks for figuring this out, Bernd.
There may be cases where the scheduler will send an old client
an app version with the same app and version # but different files.
This concerned me a bit, but it's harmless because the client
will
On 08.12.10 18:28, David Anderson wrote:
1) plan class is purely a server mechanism;
it's relevant to all client versions.
If an app_plan function references info that's only
reported by certain clients (e.g., GPU list or CPU capabilities)
then it will return false (i.e. that app version
On 09.12.10 10:07, Bernd Machenschalk wrote:
On 08.12.10 18:28, David Anderson wrote:
1) plan class is purely a server mechanism;
it's relevant to all client versions.
If an app_plan function references info that's only
reported by certain clients (e.g., GPU list or CPU capabilities)
then it
My last message was wrong.
Clients before 6.2 (early 2008) didn't know about plan class;
they assumed app versions are uniquely identified by
(app, version) rather than (app, version, plan class)
Hence the scheduler only sends app versions with no plan class
(i.e., single-CPU app versions) to
Although v6.2 and above have been around for a long time, well over two
years, some issues like http://boinc.berkeley.edu/trac/ticket/652 render it
unusable on certain hosts.
My last message was wrong.
Clients before 6.2 (early 2008) didn't know about plan class;
they assumed app versions
On 08-Dec-2010 3:07 PM, Bernd Machenschalk wrote:
If I understand correctly, the CPU capabilities are reported by recent clients
in p_features in the scheduler request.
1. This tag was added with a certain version of the BOINC client, right? Do
you
happen to know in which version this was
Hi!
1. I'm not fully aware of how the client interacts with the scheduler
regarding plan classes. I'd need to send different Apps to clients that
do support plan classes (= 6.2?) and those which don't. How do I do
this? Will a generic plan class (that doesn't actually e.g. check the
CPU
1) plan class is purely a server mechanism;
it's relevant to all client versions.
If an app_plan function references info that's only
reported by certain clients (e.g., GPU list or CPU capabilities)
then it will return false (i.e. that app version won't be sent).
2) clients report all the
David Anderson wrote, On 12/8/10 6:28 PM:
1) plan class is purely a server mechanism;
it's relevant to all client versions.
If an app_plan function references info that's only
reported by certain clients (e.g., GPU list or CPU capabilities)
then it will return false (i.e. that app version
