My RPMs:
boinc-client-6.2.15-1.20080818svn.fc8
boinc-manager-6.2.15-1.20080818svn.fc8

I had a terminal open when I installed the RPMs, and was cd'd away from /home/USER. The install dropped:
all_projects_list.xml
client_state_prev.xml
client_state.xml
gui_rpc_auth.cfg
lockfile
time_stats_log
into that current directory. I've *never* seen an RPM install do that before, in ten years or so. It's a Bad Thing.

It also dropped a file named '.BOINC Manager' into /home/USER. Spaces in the name of a dotfile?!?. That would be a Worse Thing. Using spaces in file names, on Unixy operating systems is bad practice, and wasn't done in the rest of the files (as seen above) where an underscore was used, which is the common practice. For those new to Unix, spaces can mess up backup scripts, etc., as spaces are treated as separators by many Unix/Linux command line programs, which might fail in surprising ways as they try to treat 'BOINC' and 'Manager' as two different files.

'.BOINC Manager' is just a config file, like the XML files. It would seem better to create a directory /home/USER/.boinc, as /home/USER/.adobe, etc., do, and drop all these user non-executable files in one place, without cluttering /home/USER. Some Unix folk like to keep their files *very* well organized, especially if they do much work from a console, xterm, etc.

Looking at:
http://setiathome.berkeley.edu/tech_news.php
and seeing references to 'Fedora', SELinux, and such, I would imagine they're running a mixed bag of something line CentOS or RHEL, maybe Scientific Linux, along with Fedora and Solaris. So these errors are surprising.

I still don't have it running, due to a problem with RPC (the Wiki is wrong, WRT Fedora 8, at least). But that should be in a different thread, and it's late.

Regards,

gregm

They've mucked up BOINC 6. I'm sticking with version 5 until things clear up...probably around BOINC 6.4. I'm running Fedora 8:
boinc-manager-5.10.45-14.20080315svn.fc8
boinc-client-5.10.45-14.20080315svn.fc8

Inside /etc/init.d/boinc-client:
BOINCOPTS="--daemon --allow_remote_gui_rpc --check_all_logins"

I think, it's the best to contact the maintainer of the RPM package an point them to this problem.