this information helps!
the Tutorial i found sayed i use email and password after.

but
a) i still can't detach a project
b) they are two account key a strong and a weak one

which should i use?

have a nice day
vinc

'Strong' would be normal if it is a computer under your direct control.

'Weak' would be better for a shared or public computer, or if you have permission to install BOINC on a machine belonging to somebody else.

Thanks for your feedback

i have
boinccmd --project_attach http://lhcathome2.cern.ch/vLHCathome 122019_5b2d63a9b119c58cpartWeakCode

Error -155: authentication error

have a nice day
vinc

---

OpenVZ virtuell Container with...
25GB disk / 2GB RAM / Debian-7.0 (with daily apt-get update)

boinccmd, built from BOINC 7.0.27

both way removing i got a error

root@3ct16:~# boinccmd --project http://www.climateprediction.net detach
Error -155: authentication error
root@3ct16:~# boinccmd --project http://climateprediction.net detach
Error -155: authentication error

to attach it
root@3ct16:~# boinccmd --project_attach http://climateprediction.net mymail@kozo.ch password
Error -155: authentication error

so i belive i should find out whats wrong with error -155

You're not doing it from directory that contains the client, Because of that you're got to supply the password to access that directory and you're not doing that:

http://boinc.berkeley.edu/wiki/Boinccmd_tool

The usage of boinccmd is:

boinccmd [--host hostname] [--passwd passwd] command

If you run boinccmd in the same directory as the BOINC client, you don't need to supply either a host name or a password.

Otherwise you need to supply (as password) the string stored in the file gui_rpc_auth.cfg in the client's data directory. If you run boinccmd remotely you also need to configure the client to accept remote control.

hostname can be a domain name, an IPv4 address, or an IPv6 address. If the client uses a non-default GUI RPC port, you can specify it as hostname:port, IPv4_addr:port, or [IPv6_addr]:port.

If you use the bash shell, you may find this command completion script useful.

So try:

boinccmd --passwd passwd --project http://climateprediction.net detach

Claggy

Bump.

If you don't supply the password from the gui_rpc_auth.cfg file, you don't get to control:

http://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely

Access control for GUI RPC

GUI RPCs are divided into two categories:

Status operations which return information about tasks, project, etc.
Control operations which change the state of BOINC (suspend/resume, add project, etc.).

Some GUI RPCs are authenticated with a GUI RPC password. This is stored in the file gui_rpc_auth.cfg in the BOINC data directory. On a multiuser computer, this should be protected against access by other users. When BOINC client first runs, it generates a random password. You can change it if you like; max length is 255 characters.

Local access

A "local" RPC is one that comes from the computer where the BOINC client is running (but perhaps from a different logged-in user).

Local status RPCs are not authenticated. On a multiuser computer, a user can see the status of any other user's BOINC client.

Local control RPCs are authenticated using the GUI RPC password.

Claggy

Hello
i killed the virtuell container and set up new.
Installad Boinc Client and added the

boinccmd --project_attach http://setiathome.berkeley.edu [and Key]

Now no error and it startet working.

Thanks a lot for the support

boinccmd with hostname and password is not necessary as long you are direct conectet with a Terminal like Tera Term

have a nice day
vinc

---

OpenVZ virtuell Container with...
25GB disk / 2GB RAM / Debian-7.0 (with daily apt-get update)

boinccmd, built from BOINC 7.0.27