Question for you all... What are you missing from the FAQs that you want added?
Easy question, difficult to answer perhaps. :-)

I'm having a very hard time figuring out how to set up BOINC Manager at my FSC ESPRIMO Mobile V5535 with Fedora 9 :(

Accourding to the BOINC site, i installed it with "yum install boinc-client boinc-manager" as root:

[root@localhost ~]# yum install boinc-client boinc-manager
Geladene Plugins: refresh-packagekit
Einrichten des Installationsprozess
Analysiere Installationsargumente des Pakets
Löse Abhängigkeiten auf
--> Führe Transaktionsprüfung aus
---> Paket boinc-manager.i386 0:5.10.45-14.20080315svn.fc9 gesetzt um aktualisiert zu werden
--> Verarbeite Abhängigkeiten: libwx_gtk2u_core-2.8.so.0(WXU_2.8) für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_gtk2u_richtext-2.8.so.0 für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_gtk2u_adv-2.8.so.0(WXU_2.8) für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_gtk2u_xrc-2.8.so.0 für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_gtk2u_adv-2.8.so.0 für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_gtk2u_core-2.8.so.0 für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_gtk2u_aui-2.8.so.0 für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_baseu_net-2.8.so.0(WXU_2.8) für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_baseu_xml-2.8.so.0 für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_baseu-2.8.so.0 für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_gtk2u_qa-2.8.so.0 für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_gtk2u_html-2.8.so.0 für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_baseu_net-2.8.so.0 für Paket: boinc-manager
--> Verarbeite Abhängigkeiten: libwx_baseu-2.8.so.0(WXU_2.8) für Paket: boinc-manager
---> Paket boinc-client.i386 0:5.10.45-14.20080315svn.fc9 gesetzt um aktualisiert zu werden
--> Führe Transaktionsprüfung aus
---> Paket wxGTK.i386 0:2.8.7-2.fc9 gesetzt um aktualisiert zu werden
--> Verarbeite Abhängigkeiten: libSDL-1.2.so.0 für Paket: wxGTK
---> Paket wxBase.i386 0:2.8.7-2.fc9 gesetzt um aktualisiert zu werden
--> Führe Transaktionsprüfung aus
---> Paket SDL.i386 0:1.2.13-3.fc9 gesetzt um aktualisiert zu werden
--> Abhängigkeitsauflösung beendet

Abhängigkeiten aufgelöst

=============================================================================
 Paket                   Arch       Version          Repository        Grösse
=============================================================================
Installieren:
 boinc-client            i386       5.10.45-14.20080315svn.fc9  updates           835 k
 boinc-manager           i386       5.10.45-14.20080315svn.fc9  updates           1.6 M
Installiert für Abhängigkeiten:
 SDL                     i386       1.2.13-3.fc9     fedora            226 k
 wxBase                  i386       2.8.7-2.fc9      fedora            673 k
 wxGTK                   i386       2.8.7-2.fc9      fedora            3.7 M

Transaktionszusammenfassung
=============================================================================
Installieren          5 Pakete(e)         
Aktualisieren       0 Pakete(e)         
Enfernen               0 Paket(e)         

Gesamte Downloadgrösse: 7.1 M
Ist dies in Ordnung? [j/N] :j
Lade Pakete herunter:
(1/5): SDL-1.2.13-3.fc9.i386.rpm                         | 226 kB     00:00     
(2/5): wxBase-2.8.7-2.fc9.i386.rpm                       | 673 kB     00:00     
(3/5): boinc-client-5.10.45-14.20080315svn.fc9.i386.rpm  | 835 kB     00:22     
(4/5): boinc-manager-5.10.45-14.20080315svn.fc9.i386.rpm | 1.6 MB     00:17     
(5/5): wxGTK-2.8.7-2.fc9.i386.rpm                        | 3.7 MB     00:03     
Führe rpm_check_debug durch
Führe Verarbeitungsstest durch
Verarbeitungstest beendet
Verarbeitungstest erfolgreich
Führe Verarbeitung durch
  Installieren   : wxBase                                            [1/5] 
  Installieren   : SDL                                               [2/5] 
  Installieren   : wxGTK                                             [3/5] 
  Installieren   : boinc-client                                      [4/5] 
  Installieren   : boinc-manager                                     [5/5] 

Installiert: boinc-client.i386 0:5.10.45-14.20080315svn.fc9 boinc-manager.i386 0:5.10.45-14.20080315svn.fc9
Abhängigkeit installiert: SDL.i386 0:1.2.13-3.fc9 wxBase.i386 0:2.8.7-2.fc9 wxGTK.i386 0:2.8.7-2.fc9
Komplett!
[root@localhost ~]#

Then i tried to add my projects to the manager, but only got the error:

[b]BOINC Manager - Verbindungsstatus[/b]
BOINC Manager ist augenblicklich nicht mit mit dem BOINC client
verbunden. Bitte benutzen Sie die 'Datei\Computer auswählen ...'
Menüoption um die Verbindung mit einem BOINC Client neu aufzubauen.
Wenn Sie keinen anderen Computer fernsteuern wollen, dann lassen
Sie die Felder 'Computername und Passwort leer, oder benutzen Sie
'localhost' als Computername..

MfG, MEX

---

0xFF

Then i tried to add my projects to the manager, but only got the error:

[b]BOINC Manager - Verbindungsstatus[/b]
BOINC Manager ist augenblicklich nicht mit mit dem BOINC client
verbunden. Bitte benutzen Sie die 'Datei\Computer auswählen ...'
Menüoption um die Verbindung mit einem BOINC Client neu aufzubauen.
Wenn Sie keinen anderen Computer fernsteuern wollen, dann lassen
Sie die Felder 'Computername und Passwort leer, oder benutzen Sie
'localhost' als Computername..

MfG, MEX

http://boinc.berkeley.edu/wiki/Installing_on_Linux#Fedora_7_and_up

That is, if I think the message is saying what it is.

---

Kathryn :o)

http://boinc.berkeley.edu/wiki/Installing_on_Linux#Fedora_7_and_up

That is, if I think the message is saying what it is.

Sadly this doesnt help, although the message is saying what you think :(

I followed your link and tried to open /var/lib/boinc/gui_rpc_auth.cfg in a text editor (the long string of characters is the GUI RPC password) as root on my FSC ESPRIMO Mobile V5535 with Fedora 9.

But there are no files in /var/lib/boinc at all although the directory exists !

MfG, MEX

---

0xFF

It's made by BOINC each time it starts up. If your BOINC never started up, it hasn't been made. So make one yourself and add a password into it. Just at the top line, do not end with a line break (Enter).

Then start BOINC. If BOINC Manager still gives problems, go Advanced view->Advanced->Select computer. Fill in localhost and the password you just set in the gui_rpc_auth.cfg file. Click OK. That should fix it.

Also do make sure that if you have firewall software on that computer, that you allowed boinc and boincmgr through it. Typically on port 31416.

---

It's made by BOINC each time it starts up. If your BOINC never started up, it hasn't been made. So make one yourself and add a password into it. Just at the top line, do not end with a line break (Enter).

Then start BOINC.
...

I CANT START BOINC !

Obviously "yum install ..." didnt work as it should on my V5535 with Fedora 9, as i also dont have a group boinc !

MfG, MEX

---

0xFF

Reposting part of a hidden post, as this part was new.
MEX wrote:

As not even a BOINC group exists, i assume that the installation of the client didnt work, although yum had told me that it had done everything :(

MfG, MEX

PS: Does anyone know WHO is responsible for the RPM which didnt install the client on my V5535, so that i can ask this guy to fix this problem for newer users, so that they dont have the same problem as i ?

Reposting part of a hidden post, as this part was new.
MEX wrote:

As not even a BOINC group exists, i assume that the installation of the client didnt work, although yum had told me that it had done everything :(

MfG, MEX

PS: Does anyone know WHO is responsible for the RPM which didnt install the client on my V5535, so that i can ask this guy to fix this problem for newer users, so that they dont have the same problem as i ?

How are you determining that there is no boinc user/group?

---

Kathryn :o)

http://boinc.berkeley.edu/wiki/Installing_on_Linux#Fedora_7_and_up

It seems that the order in which to do the steps mentioned in the link above isnt correct.
I first had to start the client as root before being able to change the GUI RPC password:

[mex@localhost ~]$ su
Passwort: 
[root@localhost mex]# /sbin/service boinc-client start
The BOINC client requires initialization (no projects attac[WARNUNG]
Starting BOINC client as a daemon:                         [  OK  ]
[root@localhost mex]#

After stopping the boinc-client, i was able to change the GUI RPC password and add the user mex to the group boinc with "gedit /etc/group" and did the other steps which shold allow me to connect to "localhost" without having to use a password.

But now i get the following message when i try to connect the manager to the client:

[b]BOINC Manager - Verbindungsfehler[/b]
Das eingegebene Passwort ist falsch. Bitte erneut versuchen.

MfG, MEX

PS: Suddenly, after switching to "English U.S." as language for the manager, and restarting the manager, i was able to connect to the client and download a WU for SETI@home : http://setiathome.berkeley.edu/result.php?resultid=919440442

---

0xFF

MEX wrote:

As not even a BOINC group exists, I assume that the installation of the client didn't work, although yum had told me that it had done everything :(

I wrote the wiki article on installing on Fedora from repositories.
...
Thanks for discovering the error and posting about it otherwise it might never have been fixed.

Maybe I am just too stupid :rollingeyes:
... but now I have 2 more problems:

1. manager cant connect to the client unless I go to EXTRAS and connect manually to localhost AND enter the password ( this is annoying but not a big problem )

2. client cant connect to the internet, unless I restart it as su with root rights !
This is a BIG problem as I want to start it at boot so that it is running whenever my computer is running F9.
Obviously the client started at boot isn't allowed to connect to the internet.
How can I give the client the necessary rights ?

MfG, MEX

PS: I didn't see the boinc group as I was filtering system users & groups ... as soon as I removed the hook to filter these, a lot of groups and users showed up, including boinc ( although I am no new Linux user, it is several years since I had to administrate a Linux )

---

0xFF

MEX wrote:

As not even a BOINC group exists, I assume that the installation of the client didn't work, although yum had told me that it had done everything :(

I wrote the wiki article on installing on Fedora from repositories.
...
Thanks for discovering the error and posting about it otherwise it might never have been fixed.

Maybe I am just too stupid :rollingeyes:
... but now I have 2 more problems:

1. manager cant connect to the client unless I go to EXTRAS and connect manually to localhost AND enter the password ( this is annoying but not a big problem )

2. client cant connect to the internet, unless I restart it as su with root rights !
This is a BIG problem as I want to start it at boot so that it is running whenever my computer is running F9.
Obviously the client started at boot isn't allowed to connect to the internet.
How can I give the client the necessary rights ?

MfG, MEX

PS: I didn't see the boinc group as I was filtering system users & groups ... as soon as I removed the hook to filter these, a lot of groups and users showed up, including boinc ( although I am no new Linux user, it is several years since I had to administrate a Linux )

Your 1 will happen unless you create that symlink.

It really sounds like the package didn't install properly. There should be an init.d script that starts the client at boot (but not the manager).

If you don't mind being fiddly, you can achieve the same behavior installing it by hand. You'll have to update BOINC on your own, but if the package isn't working for you, then this may help work out why.

http://www.spy-hill.net/~myers/help/boinc/unix.html

PS: You are not too stupid :-)

---

Kathryn :o)

1. manager cant connect to the client unless I go to EXTRAS and connect manually to localhost AND enter the password ( this is annoying but not a big problem )

2. client cant connect to the internet, unless I restart it as su with root rights !
This is a BIG problem as I want to start it at boot so that it is running whenever my computer is running F9.
Obviously the client started at boot isn't allowed to connect to the internet.
How can I give the client the necessary rights ?

Your 1 will happen unless you create that symlink.

It really sounds like the package didn't install properly. There should be an init.d script that starts the client at boot (but not the manager).

If you don't mind being fiddly, you can achieve the same behavior installing it by hand. You'll have to update BOINC on your own, but if the package isn't working for you, then this may help work out why...

I did create a symlink, but obviously something didnt work as it should :( which surley is my fault ;)

How can i view this init.d script from the clients RPM ?

I asume that the clients RPM isnt a "real" RPM, but only copies the clients files into the right place and that the maintainer thought that everyone is linux-literate enough to do the rest himself :(

MfG, MEX

PS: I try to repair the faulty installation of the clients RPM, so that i can use yum for updating later.
Because of this i still have the problem:
How can i give the client the right to connect to the www, even if nobodfy is logged on ?
Into which groups do have to add the user boinc ?

---

0xFF

How can i give the client the right to connect to the www, even if nobodfy is logged on ?
Into which groups do have to add the user boinc ?

The wiki article says add your username to the boinc group. If you added the boinc user to other groups then you did that step wrong.

Also, you may have to modify the SELinux settings (if you're using SELinux) to give users in the boinc group access to port 31416.

I added my username to the boinc group correct in the first try (I am not THAT stupid :rolleyes: ).
But I assume that I made a fault with the link, how can I check that the link is correct ( maybe he points to a old version of the file as I used gedit to change the password later ) ?

The hint with SElinux has a high propability to solve my problem, isn't SElinux new to Fedora since release 9 ?
( that might be the reason that I am the first who complains about this )

How do i give the boinc group access to port 31416 ?
What is this port used for ?

MfG, MEX

PS: I have edited http://boinc.berkeley.edu/wiki/Installing_on_Linux#Fedora_7_and_up to add your hint, and moved the start of the client BEFORE editing the GUI RPC password.

---

0xFF

Also, you may have to modify the SELinux settings (if you're using SELinux) to give users in the boinc group access to port 31416.

In the wiki I read "Enter chmod g+r /var/lib/boinc/gui_rpc_auth.cfg (change the permissions on /var/lib/boinc/gui_rpc_auth.cfg to allow group read)"
Can it be that I have to do a chmod g+w to /var/lib/boinc or some of the files in this directory to solve my problem, like mentioned in http://lledgerock.com/boinc_logs/%23boinc.2008-06-20.log.html ?

[mex@localhost lib]$ ls boinc -als
insgesamt 1000
  4 drwxr-xr-x  4 boinc boinc   4096 18. Jul 21:19 .
  4 drwxr-xr-x 34 root  root    4096 14. Jul 16:02 ..
  4 -rw-r--r--  1 boinc boinc    431 17. Jul 21:02 account_boinc.iaik.tugraz.at_sha1_coll_search.xml
  4 -rw-r--r--  1 boinc boinc    376 17. Jul 21:04 account_dist.ist.tugraz.at_cape5.xml
  4 -rw-r--r--  1 boinc boinc   3386 17. Jul 21:00 account_einstein.phys.uwm.edu.xml
  4 -rw-r--r--  1 boinc boinc    360 17. Jul 21:00 account_lhcathome.cern.ch_lhcathome.xml
  4 -rw-r--r--  1 boinc boinc    441 17. Jul 21:00 account_orbit.psi.edu_oah.xml
  4 -rw-r--r--  1 boinc boinc   2794 17. Jul 21:01 account_setiathome.berkeley.edu.xml
  4 -rw-r--r--  1 boinc boinc    371 16. Jul 15:48 account_setiweb.ssl.berkeley.edu_beta.xml
 20 -rw-r--r--  1 boinc boinc  16761 16. Jul 14:12 all_projects_list.xml
 72 -rw-r--r--  1 boinc boinc  65602 18. Jul 21:19 client_state_prev.xml
 72 -rw-r--r--  1 boinc boinc  65602 18. Jul 21:19 client_state.xml
  8 -rw-r--r--  1 boinc boinc   5141 16. Jul 15:13 get_current_version.xml
  4 -rw-r--r--  1 boinc boinc    181 16. Jul 15:54 get_project_config.xml
  4 -rw-r--r--  1 boinc boinc    992 16. Jul 15:13 global_prefs.xml
  4 -rw-r-----  2 boinc boinc      9 16. Jul 14:58 gui_rpc_auth.cfg
  4 -rw-r-----  1 root  root      12 16. Jul 14:58 gui_rpc_auth.cfg~
...

MfG, MEX

PS: Found a explanation for port 31416 in http://setiathome.berkeley.edu/forum_thread.php?id=17525&nowrap=true#147111 and http://www.archivum.info/debian-bugs-closed@lists.debian.org/2007-04/msg03584.html

Which still leaves the question HOW do i give boinc access to port 31416 to solve my problem with SELinux ?

---

0xFF

The hint with SElinux has a high propability to solve my problem, isn't SElinux new to Fedora since release 9 ?
( that might be the reason that I am the first who complains about this )

Nope, it's definitely in 7. I caused a kernel panic on reboot by making a mistake editing the config file.

---

Kathryn :o)

Upstart Init Daemon

Fedora 9 uses the Upstart init daemon as a replacement for System V init. The benefit of this is that Upstart has a more sophisticated idea of how to to trigger and manage services. For Fedora this is particularly useful as it will help us to improve our boot and shutdown processes, streamlining a lot of what currently happens.

All current init scripts should run without errors. However, any customizations to /etc/inittab (except initdefault) will need to be ported to upstart...

Maybe the new UPSTART is causing my problems with boinc_client started at boot beeing unable to connect to the www
... unless I restart boinc_client as root :(

Can someone please check if the init scripts of boinc_client for F9 are compatible to Upstart ?

MfG, MEX

PS: Maybe boinc_client is started too early at boot, and remembers that it cant connect to the www unless it is restarted ...

---

0xFF

Upstart Init Daemon

Fedora 9 uses the Upstart init daemon as a replacement for System V init. The benefit of this is that Upstart has a more sophisticated idea of how to to trigger and manage services. For Fedora this is particularly useful as it will help us to improve our boot and shutdown processes, streamlining a lot of what currently happens.

All current init scripts should run without errors. However, any customizations to /etc/inittab (except initdefault) will need to be ported to upstart...

Maybe the new UPSTART is causing my problems with boinc_client started at boot beeing unable to connect to the www
... unless I restart boinc_client as root :(

Can someone please check if the init scripts of boinc_client for F9 are compatible to Upstart ?

MfG, MEX

PS: Maybe boinc_client is started too early at boot, and remembers that it cant connect to the www unless it is restarted ...

Interesting theory.

Can you take the init.d script out of the boot sequence? And then see if you start the client with

/etc/init.d/boinc start

. You'll need to be root to do that, but then the init.d script should start BOINC up under the user boinc.

---

Kathryn :o)

BTW: I've emailed Eric Myers (who developed the rpm) and Milos (who packaged BOINC for Fedora) and cc-ed it to David and Rom. We'll see what they have to say.

I just wanted to let you know, I'm trying to get people in here who actually know something (unlike me).

---

Kathryn :o)

BTW: I've emailed Eric Myers (who developed the rpm) and Milos (who packaged BOINC for Fedora) and cc-ed it to David and Rom. We'll see what they have to say.

I just wanted to let you know, I'm trying to get people in here who actually know something (unlike me).

I just found the link to this page in my bookmarks... http://fedoraproject.org/wiki/User:Mjakubicek/HowToUseBoinc. See the Discussion link there.

Note, you need to create an account (which is kinda hard to find).

But Dag, is there anything in the discussion page there? Or am I just being blind again?

---

Kathryn :o)

Note, you need to create an account (which is kinda hard to find).

But Dag, is there anything in the discussion page there? Or am I just being blind again?

What type of account are you talking about ? ... A BOINC account ? ... the account boinc in f9? ... my useraccount which I have added to the group boinc in f9 ? ...

I am participating in SETI@home since the last century, and have used a linux client without problems for the CLASSIC application years ago.

After installing f9 on my FSC ESPRIMO Mobile V5535, as I wasn't satisfied with the support of Ubuntu for my PS3 because I want to use the same distribution on both computers with BOINC, I installed BOINC with "yum install boinc-client boinc-manager" as mentioned in http://boinc.berkeley.edu/wiki/Installing_on_Linux#Fedora_7_and_up and changed the GUI RPC password to something shorter and easier to remember. I also created a link to /var/lib/boinc/gui_rpc_auth.cfg in my home directory and added my username to the boinc group.

Until now I didn't modify the SELinux settings to give users in the boinc group access to port 31416 (as I don't know how to do this), or anything else.

My current status with BOINC and f9 on my V5535 is that I still have to connect the manager manually to localhost in its Extras, and that the client isn't able to connect to the www:

Die 22 Jul 2008 11:50:27 CEST||Starting BOINC client version 5.10.45 for i686-pc-linux-gnu
Die 22 Jul 2008 11:50:27 CEST||log flags: task, file_xfer, sched_ops
Die 22 Jul 2008 11:50:27 CEST||Libraries: libcurl/7.18.2 NSS/3.12.0.3 zlib/1.2.3 libidn/0.6.14
Die 22 Jul 2008 11:50:27 CEST||Executing as a daemon
Die 22 Jul 2008 11:50:27 CEST||Data directory: /var/lib/boinc
Die 22 Jul 2008 11:50:27 CEST||Processor: 1 GenuineIntel Intel(R) Celeron(R) CPU          540  @ 1.86GHz [Family 6 Model 22 Stepping 1]
Die 22 Jul 2008 11:50:27 CEST||Processor features: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx lm constant_tsc up arch_perfmon pebs bts pni monitor ds_cpl tm2 ssse3 cx16 xtpr lahf_lm
Die 22 Jul 2008 11:50:27 CEST||OS: Linux: 2.6.25.10-86.fc9.i686
Die 22 Jul 2008 11:50:27 CEST||Memory: 2.71 GB physical, 3.99 GB virtual
Die 22 Jul 2008 11:50:27 CEST||Disk: 62.98 GB total, 56.37 GB free
Die 22 Jul 2008 11:50:27 CEST||Local time is UTC +2 hours
Die 22 Jul 2008 11:50:27 CEST|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 1482516; location: home; project prefs: default
Die 22 Jul 2008 11:50:27 CEST|SHA-1 Collision Search Graz|URL: http://boinc.iaik.tugraz.at/sha1_coll_search/; Computer ID: 31994; location: home; project prefs: default
Die 22 Jul 2008 11:50:27 CEST|Rectilinear Crossing Numbers|URL: http://dist.ist.tugraz.at/cape5/; Computer ID: 39216; location: home; project prefs: default
Die 22 Jul 2008 11:50:27 CEST|lhcathome|URL: http://lhcathome.cern.ch/lhcathome/; Computer ID: 9703324; location: home; project prefs: default
Die 22 Jul 2008 11:50:27 CEST|orbit@home|URL: http://orbit.psi.edu/oah/; Computer ID: 8705; location: (none); project prefs: default
Die 22 Jul 2008 11:50:27 CEST|SETI@home Beta Test|URL: http://setiweb.ssl.berkeley.edu/beta/; Computer ID: 29977; location: home; project prefs: default
Die 22 Jul 2008 11:50:27 CEST|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 4482760; location: home; project prefs: default
Die 22 Jul 2008 11:50:27 CEST||General prefs: from orbit@home (last modified 27-Jun-2008 14:48:32)
Die 22 Jul 2008 11:50:27 CEST||Host location: none
Die 22 Jul 2008 11:50:27 CEST||General prefs: using your defaults
Die 22 Jul 2008 11:50:27 CEST||Preferences limit memory usage when active to 1388.09MB
Die 22 Jul 2008 11:50:27 CEST||Preferences limit memory usage when idle to 2498.56MB
Die 22 Jul 2008 11:50:27 CEST||Preferences limit disk usage to 1.86GB
Die 22 Jul 2008 11:50:27 CEST||Running CPU benchmarks
Die 22 Jul 2008 11:50:58 CEST||Benchmark results:
Die 22 Jul 2008 11:50:58 CEST||   Number of CPUs: 1
Die 22 Jul 2008 11:50:58 CEST||   1109 floating point MIPS (Whetstone) per CPU
Die 22 Jul 2008 11:50:58 CEST||   4371 integer MIPS (Dhrystone) per CPU
Die 22 Jul 2008 11:50:59 CEST|SETI@home Beta Test|Restarting task ap_23ap08ab_B1_P0_00015_20080715_06439.wu_1 using astropulse version 434
Die 22 Jul 2008 11:51:00 CEST|lhcathome|Sending scheduler request: To fetch work.  Requesting 1324 seconds of work, reporting 0 completed tasks
Die 22 Jul 2008 11:51:01 CEST||Project communication failed: attempting access to reference site
Die 22 Jul 2008 11:51:02 CEST||Access to reference site failed - check network connection or proxy configuration.
Die 22 Jul 2008 11:51:05 CEST|lhcathome|Scheduler request failed: Couldn't resolve host name
Die 22 Jul 2008 11:51:10 CEST|orbit@home|Sending scheduler request: To fetch work.  Requesting 651 seconds of work, reporting 0 completed tasks
Die 22 Jul 2008 11:51:16 CEST|orbit@home|Scheduler request failed: Couldn't resolve host name
Die 22 Jul 2008 11:52:11 CEST|lhcathome|Sending scheduler request: To fetch work.  Requesting 1324 seconds of work, reporting 0 completed tasks
Die 22 Jul 2008 11:52:16 CEST|lhcathome|Scheduler request failed: Couldn't resolve host name
Die 22 Jul 2008 11:53:52 CEST|lhcathome|Sending scheduler request: To fetch work.  Requesting 1323 seconds of work, reporting 0 completed tasks
Die 22 Jul 2008 11:53:57 CEST|lhcathome|Scheduler request failed: Couldn't resolve host name
Die 22 Jul 2008 12:23:12 CEST|SHA-1 Collision Search Graz|Finished download of icon_krypto_01.png
Die 22 Jul 2008 12:23:12 CEST|SHA-1 Collision Search Graz|Finished download of show_01_01.png
Die 22 Jul 2008 12:23:12 CEST|SHA-1 Collision Search Graz|Started download of show_02_01.png
Die 22 Jul 2008 12:23:12 CEST|SHA-1 Collision Search Graz|Started download of show_03_01.png
Die 22 Jul 2008 12:23:13 CEST|SHA-1 Collision Search Graz|Finished download of show_02_01.png
Die 22 Jul 2008 12:23:13 CEST|SHA-1 Collision Search Graz|Finished download of show_03_01.png
Die 22 Jul 2008 12:23:13 CEST|SHA-1 Collision Search Graz|Started download of show_04_01.png
Die 22 Jul 2008 12:23:14 CEST|SHA-1 Collision Search Graz|Finished download of show_04_01.png
Die 22 Jul 2008 12:23:18 CEST|SHA-1 Collision Search Graz|Sending scheduler request: To fetch work.  Requesting 44 seconds of work, reporting 0 completed tasks
Die 22 Jul 2008 12:23:19 CEST|SHA-1 Collision Search Graz|Starting wu_sha1collisionsearchgraz_v55_1216702853_958_0
Die 22 Jul 2008 12:23:19 CEST|SHA-1 Collision Search Graz|Starting task wu_sha1collisionsearchgraz_v55_1216702853_958_0 using sha1_collisionsearch_graz version 535
Die 22 Jul 2008 12:23:23 CEST|SHA-1 Collision Search Graz|Scheduler request succeeded: got 1 new tasks
Die 22 Jul 2008 12:23:25 CEST|SHA-1 Collision Search Graz|Started download of wu_sha1collisionsearchgraz_v55_1216702853_1258
Die 22 Jul 2008 12:23:26 CEST|SHA-1 Collision Search Graz|Finished download of wu_sha1collisionsearchgraz_v55_1216702853_1258
Die 22 Jul 2008 12:25:50 CEST|orbit@home|Sending scheduler request: To fetch work.  Requesting 651 seconds of work, reporting 0 completed tasks
Die 22 Jul 2008 12:26:01 CEST|orbit@home|Scheduler request succeeded: got 0 new tasks

until I restart the client as root:

[mex@localhost ~]$ /sbin/service boinc-client restart
rm: Entfernen von „/var/lib/boinc/lockfile“ nicht möglich: Keine Berechtigung
rm: Entfernen von „/var/lock/subsys/boinc-client“ nicht möglich: Keine Berechtigung

Starting BOINC client as a daemon:  /etc/init.d/boinc-client: line 165: /var/log/boincerr.log: Keine Berechtigung
touch: kann „/var/lock/subsys/boinc-client“ nicht berühren: Keine Berechtigung
                                                           [FEHLGESCHLAGEN]
[mex@localhost ~]$ su
Passwort: 
[root@localhost mex]# ps aux | grep boinc
boinc     1982  0.1  0.1  10796  3096 ?        SNs  11:50   0:02 /usr/bin/boinc_client --daemon
boinc     2225 89.7  1.7  50584 48356 ?        RNl  11:50  24:29 astropulse_4.34_i686-pc-linux-gnu
mex       2488  0.9  0.7  58440 22420 ?        S    11:51   0:15 boincmgr
root      2627  0.0  0.0   5068   784 pts/1    S+   12:18   0:00 grep boinc
[root@localhost mex]# /sbin/service boinc-client restart
Stopping BOINC client daemon:                              [  OK  ]
Starting BOINC client as a daemon:                         [  OK  ]
[root@localhost mex]# ps aux | grep boinc
mex       2488  0.9  0.7  58444 22428 ?        S    11:51   0:16 boincmgr
boinc     2668  0.1  0.1  10692  2864 ?        SNs  12:19   0:00 /usr/bin/boinc_client --daemon
boinc     2669  107  1.6  50304 46700 ?        RNl  12:19   0:06 astropulse_4.34_i686-pc-linux-gnu
root      2674  0.0  0.0   5064   768 pts/1    R+   12:19   0:00 grep boinc
[root@localhost mex]#

MfG, MEX

---

0xFF

I just found the link to this page in my bookmarks... http://fedoraproject.org/wiki/User:Mjakubicek/HowToUseBoinc. See the Discussion link there.

If you want to set an empty password for BOINC, just paste only a newline into /var/lib/boinc/gui_rpc_auth.cfg

Maybe I have to use a empty password to solve my problem with the manager not connecting to the client automatically, like mentioned in your link ... HOW do I paste only a NEWLINE into gui_rpc_auth.cfg with gedit, or should i use another editor ( which would require which commands) ?

MfG, MEX

---

0xFF