If requested, I will add the method for Linux. p is for the random letters and numbers from the gui_rpc_auth.cfg file. g is for the port number you set for the new instance. This is the password.Įdit the 'Target' line of the BOINC2 Shortcut to include the new port # and new password (this the random letters and numbers). Example: BOINC2Ĭopy the random letters and numbers from gui_rpc_auth.cfg. Rename this to the instance of BOINC made. Next is to hook this instance to the BOINC Manager.Ĭonnecting BOINC Manager to the new instance: Now, you have another instance of BOINC running. This will start another instance of BOINC which can now be setup to download and run more WUs to bunker with. "c:\Program Files\BOINC\boinc.exe" -allow_multiple_clients -redirectio -detach_console -gui_rpc_port 31418 -dir C:\ProgramData\BOINC2 Next, creat a batch file in the new BOINC folder. Steps to setup another instance of BOINC for bunker technique:įirst, create a new folder in C:\ProgramDataĮdit the cc_config.xml file to include the allow_multiple_clients option. Note: this technique is not useful on projects with quorum 2. This can allow a team to take a higher spot at the end before other teams can react. Usually can be seen when a team shows low output in one or two disciplines then all of a sudden a large amount of points are dumped on one project as the end date nears. The technique is even used near the end of discipline dates to gain last minute advantages as well. Once the discipline start date hits, the WUs are then off loaded from the client allowing a large amount of points to be gained at the start. The advantage of this technique is to hold many WUs that are crunch ahead of time before a discipline (BOINC project) start date occurs. The following is a technique referred to as bunkering in the Pent.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |