Hi David!

Thanks so far.

1. If the <cgi_url> isn't used, shouldn't it be removed to avoid confusion (I remember this confusion costed E@H several hours at least two times during server re-configurations)? Even less confusing, however, it would be IMHO if the index.php page would read the scheduler URL(s) from the <cgi_url> and BOINC would get rid of schedulers.txt altogether (FWIW that's what the current Drupal web code already does). For compatibility I'd make index.php checke if schedulers.txt is there, include it if it is, and only use the config when it's absent; then make make_project not create a new schedulers.txt anymore.

2. The question what the client does with multiple schedulers is still unanswered. Does it pick one? Deterministically or at random? Randomized on what, e.g. would the same Client (with the same hostid) always pick the same scheduler? What happens if one scheduler can't be reached or doesn't (fully) fulfill the work request?

Best,
Bernd


David Anderson wrote, On 10.04.13 20:28:
Bernd:
The <cgi_url> in config.xml isn't used.
You can run schedulers on multiple hosts
(each with its own feeder, using --mod).
See
http://boinc.berkeley.edu/trac/wiki/MultiHost#Runserverdaemonsandtasksonmultiplehosts
-- David

On 10-Apr-2013 2:04 AM, Bernd Machenschalk wrote:
Hi!

It looks like there are two different, independent places where a "cgi" /
"scheduler" URL is set:

- <cgi_url> in the project config
- html/user/schedulers.txt

- Digging through the code I found nothing that actually uses the URL set in the
project config. Is there anything where this is being used?

- The name "schedulers.txt" implies that is is possible to specify more than one scheduler. Is is? If so, how would you do this? How would the Client react to
that? Is any project already using this?

If anything is changed I would much prefer to configure the scheduler(s) in the
project config than in yet another file in the html tree.

Best,
Bernd


_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to