Hello!
I;m runnig text version of Boinc as a daemon on Linux machine. I have a question: does anybody know for which files Boinc client need to have access? When I run Boinc as user "boinc" and group "boinc" client won't detect amount of RAM, cann't connec to server etc. When I added user "boinc" to group "adm" it works. But this is not so good idea.. so I need to know for which system files client need to have access to work and connect correctly?
Thanks for any suggestions!

Lukas

---

Sorry, have no idea what files it tries, that depends on just way too many things. Besides, you can get at that info much easier than we can.

Have you checked your message log to see what files BOINC has problems with? User boinc and group boinc should work fine, unless you're securing things. And if you did, failed accesses get logged.

I'm making an assumption that you're talking about your Linux system running a secure kernel - thats SE Linux? If so, see some of the documentation from the SE Linux project on SourceForge. Some relevent ones:

Getting Started with SE Linux HOWTO

Writing SE Linux policy HOWTO

And from the NSA site: Configuring the SE Linux Policy.

Chapter 5 of "Getting started..." shows how to set up a new user, chapter 6 a new domain and chapter 7 explains the messages that get logged.

Thanks for suggestions... I've checked error.log file before I wrote this question. There was no message about any files / daemons, only something like "connect error, master file fetch error, etc.). But now I'll check all system security logs (it will take much time, so i didn't have time to do it before... ;-) ).
But now I think there is only way to solve this problem...
Thanks again,
Best regards, Lukas.

BTW. This system is MandrakeLinux 10.1 Off. PP+

---

> Thanks for suggestions... I've checked error.log file before I wrote this
> question. There was no message about any files / daemons, only something like
> "connect error, master file fetch error, etc.). But now I'll check all system
> security logs (it will take much time, so i didn't have time to do it
> before... ;-) ).
> But now I think there is only way to solve this problem...
> Thanks again,
> Best regards, Lukas.
>
> BTW. This system is MandrakeLinux 10.1 Off. PP+
>

Mandrake is a distribution, right?

I looked at your computers and saw three Linux systems. And since you were having file access problems, though it was with the system running an SELinux kernel. Thats this one, with the "Linux 2.6.3-4mdksecure" kernel. An SELinux kernel for a Mandrake distribution.

If we're talking about the same system, check out the links I supplied. They're very useful in setting up your secure linux system and getting applications set up to run in a secure environment.

If we're talking about your other Mandrake Linux systems, then check out the links anyways. And turn on enough logging on the box with Linux 2.6.3-4mdksecure so you can see what BOINC is accessing.

BOINC runs happily under the users group, but its installation directory and file permissions have to be appropriate for the user/group under which it's running.

My personal preference for running the core client is to do so as a cron job running under my standard login and run it within $HOME for that login.

---