When i try to start the client it says there is another instance of the program running... i do ps -e and it does not show it...

I read that removing the lockfile solves this, and it does but only when i change to root. Why?

Also... there is already a post as to how to suspend manually when running the command line version under linux. And i saw no appropriate answer...

Is it killing the process the only way?

Thanks for your help

I haven\'t had your experience with the lock file so I can\'t help you there.

As for the 2nd question, there is no way I know of to suspend without using boincmgr. But there may be some secret option I don\'t know about either.

Try a ps with your user name (ps -u [username]).

Just looked at the faq and there doesn\'t seem to a a CLI-option for suspending. Killing the BOINC-process (NEVER kill the CPDN-process) exits the client. I also suspend via the GUI-manager.

---

You can simply stop BOINC with ctrl+c, this will shut down all running projects clean.

---

Linux Users Everywhere @ BOINC

I had this problem too (on Ubuntu Linux). The BOINC directory needs to be writable by everyone (or everyone who\'s going to run BOINC).

I had this problem too (on Ubuntu Linux). The BOINC directory needs to be writable by everyone (or everyone who\'s going to run BOINC).

That didn\'t fix it properly, but I was able to get it working okay through the Debian package.

---

Problem is normally caused due to the initial installation being perfromed as root and the files all then being owned by root.

I created a boinc account and set the folder and all its contents to be boinc read/write and run the job under user boinc. any profile will do but the default of root causes a number of interesting issues.

One problem I have yet to solve (although probably straightforward) is that when not running under root I can no longer attach to a remote client . . .

---

>As for the 2nd question, there is no way I know of to suspend without using boincmgr


There is a way to do all the commands of the BoincManager in command-line:
Use boinc_cmd.
It\'s badly documented, but using the command: ./boinc_cmd -h will give you all the infos.
Of course, it\'s not as easy to use as the Manager but all the commands of the manager are available.


[arnaud@Albert BOINC]$ ./boinc_cmd -h


usage: boinc_cmd [--host hostname] [--passwd passwd] command

Commands:
--get_state show entire state
--get_results show results
--get_file_transfers show file transfers
--get_project_status show status of all projects
--get_disk_usage
<b>--result url result_name {suspend | resume | abort | graphics_window | graphics_fullscreen}
--project url {reset | detach | update | suspend | resume | nomorework | allowmorework}</b>
--project_attach url auth
--file_transfer {retry | abort} url filename
--get_run_mode
--set_run_mode {always | auto | never}
--get_network_mode
--set_network_mode {always | auto | never}
--get_proxy_settings
--set_proxy_settings
--get_messages seqno show messages > seqno
--get_host_info
--acct_mgr_rpc url name password
--run_benchmarks
--get_screensaver_mode
--set_screensaver_mode on|off blank_time {desktop window_station}
--get_project_config url
--get_project_config_poll
--lookup_account url email passwd
--lookup_account_poll
--create_account url email passwd name
--create_account_poll
--quit

The command ./boinc_cmd --get_state gives you a lot of infos about the projects, etc. Never see so much infos in command-line.

---

Arnaud

After a research on the BOINC web site:

To suspend all the projects in command-line (=suspend in Boincmanager), type:
./boinc_cmd --set_run_mode never
and to restart all the projects (=run always in BOincManager), type:
./boinc_cmd --set_run_mode always

To know the status of your your boinc (running always or suspended ?), type:
./boinc_cmd --get_run_mode

For more details about the Boinc Command tool:
http://boinc.berkeley.edu/boinc_cmd.php
Boinc-Wiki cmd infos

---

Arnaud