OC
Try these, works for me on Ubuntu:

The BOINCCMD program is the command line control program for BOINC. While you can start the BOINC client with its own set of switches, you can set these only once.

The BOINCCMD program allows you to control BOINC multiple times, especially useful for when you lack a GUI (BOINC Manager). Multiple commands per line are possible.

Usage: Boinccmd --command1 --command2 --command3

--lookup_account URL email passwd
Used to check up on your account and get your authenticator key and details sent to you.

--create_account URL email passwd name
Used to make an account at a project, using password such and so, your email address and what nickname to go on the account. Usage: boinccmd --create_account http://setiathome.berkeley.edu joe@email.com RoVeR12 Joe .. Watch out with case sensitivity on password!

--project_attach URL auth
Attach to project using your authenticator key.

--join_acct_mgr URL name password
Attach to an account manager.

--quit_acct_mgr
Quit using your current account manager.

--get_state
Show entire state.

--get_results
Show tasks. BOINC 6.12 and before.

--get_tasks
Show tasks. BOINC 7.0 and later.

--get_simple_gui_info
Show status of projects and active tasks.

--get_file_transfers
Show file transfers.

--get_project_status
Show status of all attached projects.

--get_disk_usage
Show disk usage per project attached.

--get_proxy_settings
Show proxy settings.

--get_messages [ seqno ]
Show messages, if need be output per sequence number.

--get_message_count
Show largest message sequence number.

--get_host_info
Shows details about your host, such as CPU used, Network name, operating system, disk size, etc.

--version, -V
Show core client version.

--result url task_name operation
Job operation options = suspend | resume | abort | graphics_window | graphics_fullscreen

--project URL operation
Project operation options = reset | detach | update | suspend | resume | nomorework | allowmorework

--file_transfer URL filename operation
File transfer operation options = retry | abort

--set_gpu_mode
Sets GPU mode. Options always | auto | never

--set_run_mode mode duration
Set run mode for given duration mode = always | auto | never

--set_network_mode mode duration
Set run mode for given duration mode = always | auto | never

--set_proxy_settings
Set up your proxy settings.

--run_benchmarks
Run CPU benchmarks.

--read_global_prefs_override
(Re-)Read the global_prefs_override.xml file.

--quit
Quit running the BOINC client.

--read_cc_config
(Re-)read the client configuration file (cc_config.xml).

--set_debts URL1 std1 ltd1 [URL2 std2 ltd2 ...]
Used to (re-)set the short term and long term debts of any given project. Usage: boinccmd --set_debts http://setiathome.berkeley.edu 0 0 (to reset the short term and long term debts on Seti@Home).

--get_project_config URL
Unknown

--get_project_config_poll
Unknown

--network_available
Unknown

--get_cc_status
Unknown

OldChap,

(disclaimer) I haven't tried exactly what you are suggesting, but here are some clues. The boinc executable is in the /usr/bin folder. Also in that folder are the boinccmd executable and the boincmgr executable. You should be able to start any of those executables from that folder. You can open a terminal, cd to that folder then just enter the executable name followed by the parameters that you want.

Try that and let us know what happens.

All useful info but not yet quite right.

An improvement certainly as it is not now giving me the finger, but clearly I am missing something.

I'll have another try next weekend

Thanks guys

OldChap,

Try this:

Edit /var/lib/boinc-client/gui_rpc_auth.cfg to see the value of the rpc password (you will need this when you switch BOINC manager to the second instance of BOINC)
Edit /var/lib/boinc-client/cc_config.xml
In the options sections add a line for <allow_multiple_clients>1</allow_multiple_clients>
Either restart primary boinc or read config files in primary boinc
Enter the following commands in a terminal session:

cd /var/lib
sudo mkdir boinc-client-31418
sudo cp /var/lib/boinc_client/ca-bundle.crt /var/lib/boinc-client-31418/ca-bundle.crt
sudo cp /var/lib/boinc-client/gui_rpc_auth.cfg /var/lib/boinc-client-31418/gui_rpc_auth.cfg
cd /usr/bin
sudo boinc --allow_multiple_clients --dir /var/lib/boinc-client-31418 --gui_rpc_port 31418

That should get you started. The second copy of boinc client will be running with the user of "root".

Try that and let us know how it goes.

Ta Dah !!!

Good news.

Manually added the slots folder and that resolved the "could not open" issue

and the "bind to port" issue was fixed by moving to a different port (I used 60201 as I have used that one before in windows)

I only have one issue reported still and that may not be an issue as such I just have to wait and see.

The report was:

dir_open: Could not open directory '/dev/input/mice' from '/var/lib/boinc-client2-30301

That said I have now connected to BoincTasks and added project

With cores divided between boinc-client and boinc-client2 I can now start to experiment with settings and see the real time difference between the two

Many thanks for your help in getting me here captainjack