continuous Boinc communication
22 Nov 2006 12:52:55 UTC
Topic 192103
(moderation:
I've a qn on Boinc, but can't find where to direct it. If anyone can point me in the right direction, or even answer it, I'd be grateful.
I've noticed that boincmgr.exe and boinc.exe are continuously sending and receiving data - a couple of hundred bytes/sec out and in for each task. I only process E@H. Boinc ver 5.4.11. What is the data that's going back and forth?
Mike
continuous Boinc communication
)
It's the data you can see in boincmgr, such as state of tasks, progress of tasks, disk free, BOINC messages, ...
Metod ...
To allow for the ability to
)
To allow for the ability to remotely control other machines with BOINC Manager, they have written it to talk to BOINC client over TCP/IP. This is normal communication of the client sending the manager the state of what is going on. BOINC Client can be run without the manager. I do that on most of my machines. It save the processing time of always updating the manager, and gives me a little more memory back. I only open the manager when I need to make some changes.
Thanks Metod, PB Pooh, that
)
Thanks Metod, PB
Pooh, that looks interesting. How do you close and reopen Boinc mgr?
Mike
RE: Thanks Metod, PB Pooh,
)
Depends on how you installed it. I installed all mine as a service, so BOINC client automatically starts at bootup. I took out BOINCMGR from the start up folder, and just run it manually when I need it. Then I use "File-Exit" to shut it down. If you installed it as a share or single user, then you need to change the startup folder to run BOINC (I am not sure what options you need, but I know you need some). I am unsure how stopping the manager when install in this fashion does to the client, but if you use the right options I believe it should stay running.
Thanks Pooh. Enough info
)
Thanks Pooh. Enough info there for me to experiment and figure it out for my setup.
Mike
It's easy enough to do for a
)
It's easy enough to do for a single or shared installation. All you need to do is remove the BOINC icon from the startup folder (save it somewhere for NT based Windows, you can disable it in msconfig for 9x).
Then start the Core Client from the Run dialog with:
\\boinc
If you want to be able to look at it from a different machine, add the switch:
-allow_remote_gui_rpc
to the command.
HTH,
Alinator
BTW, this is called command line mode (big surprise there :-) ). You exit BOINC with Ctrl Pause/Break, and can toggle between pause and run with Ctrl C. However there is a bug so the toogle only pauses but doesn't resume with the current recommended release. It is fixed in the 5.7.x Alphas.
Thanks for this tip Alinator,
)
Thanks for this tip Alinator, I hadn't discovered the CLI mode for Windows till now. It also seems that you need to add -detach to prevent the console window from showing up.
RE: Thanks for this tip
)
Thats correct. However, I find it easier (and a little safer) to leave the client attached to the console. The reason is it's a reminder to me to shutdown BOINC before logging off the account or powering down the host. The catch is exiting from BOINC Manager does not cause the client to quit in CLI mode. If it's detached from the console your only "safe" option is to send the --quit command from boinccmd (the console command interface utility). Killing the client from Taskmanager (or Shutting Down) may cause the currently running result to restart from scratch under some circumstances.
HTH,
Alinator
Note: This BOINC start/stop tip doesn't seem to be an issue with a Service install, just when running in CLI mode.