Posts by Hermanoid

1) Message boards : BOINC client : Starting BOINC clients and attaching projects, except from a single terminal (Message 80522)
Posted 29 Aug 2017 by Hermanoid
Post:
Thanks BobCat, that's a link I didn't know about.

However, it doesn't look like --detach_console will complete the Initialization process on the client before returning control, so running a control command like
boinccmd --project_attach URL WeakKey

...immediately after starting the client will almost certainly cause the control command to be executed before the client is initialized, resulting in an error.

If --detach_console is to work, there will have to be a subsequent command to wait until the client is started.

All of that said, I think the --attach_project command (on the client itself) will work just fine.

Thanks for the help!
2) Message boards : BOINC client : Starting BOINC clients and attaching projects, except from a single terminal (Message 80489)
Posted 27 Aug 2017 by Hermanoid
Post:
Hello all,

I have a bit of a "challenge case" here.

I'm trying to set up an array of BOINC clients (with some spare $$$ I got for free in an azure deal), from what amounts to a single command prompt/terminal.

Alas, there is a difficulty: The BOINC client runs effectively forever , and it blocks the executing command line/terminal from executing other commands whilst it runs. Since Boinccmd needs a running client to attach projects and do control operations to, it is impossible to attach BOINC projects to the client from the same terminal as the client.

The logical solution to this is to run the client seperately:
start boinc.exe

but, with that, subsequent commands to configure/attach/otherwise control the BOINC client will probably execute before the the client is fully initialized (A race condition, as they call it).

I have found what seem to be three different option to solving this, all of which could work, none of which I know how to implement:
Option 1, attach beforehand:
$ setting-dinglehopper --project-attach URL WEAKKEY
$ boinc.exe


Option 2, attach in the same command:
$ boinc.exe --project-attach URL WEAKKEY

EDIT: I did figure out how to do this one, although apparently it is not recommended, and I'd like a better solution.

or Option 3, somehow wait for the client to start:
$ start boinc.exe
$ boinccmd --wait-for-boinc-client?
$ boinccmd -project-attach URL WEAKKEY


If none of these work, I could work something out using remote RPCs... but avoiding that would be so~ much easier.

Batch (.bat) files ARE a possibility. The operating system of choice is Linux, although Windows is a possibility as well. (This is Microsoft Azure we're talking about here).

Thanks for any tips!
Lucas Niewohner (or Hermanoid, whichever you prefer)



Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.