Questions and Answers :
Getting started :
Repost: Storing BOINC files somewhere other than ~/
Message board moderation
Author | Message |
---|---|
N/A Send message Joined: 18 May 01 Posts: 3718 Credit: 93,649 RAC: 0 |
This is a repost of a question I asked originally in the Mac OS Q&A, but applies to other platforms. I've found that all of the BOINC ancillary files and folders are being stored in ~/ regardless of wherever I store the executable. How do I tell BOINC to store its files elsewhere? |
Jean-Pierre Godet Send message Joined: 12 Sep 99 Posts: 4 Credit: 41,648 RAC: 0 |
Hello, friend ! I don't understand why, as here, but with another OS, I runned first BOINC as root in /boinc directory, and all the stuff was lying in this directory. Then I tried to use it in an other directory (/home/godetj/ files/BOINC) as a "normal" user (not the "super user" root)and all the files and subdirectories are now in this directory. Now BOINC is running as a background task in a special virtual console for it (VT7) and the owner of the files and subdirectories generated by BOINC and SETI client are now root, but are still remainning in this directory. This is on a Linux machine (Slackware 10.0 with kernel 2.4.26). May be your MacOS doesn't permit to a "normal" user to put files in /usr ? and force BOINC to use the home directory of the user owning and running BOINC... Jean-Pierre |
Keith J. Schultz Send message Joined: 6 Apr 01 Posts: 49 Credit: 10,408 RAC: 0 |
Hi Neo, The answer is simple. boinc stores you file in the current working directory! Not in the directory where boinc is stored. So you have to cd to the directory of where you want your to be stored. Here is a script to do that: cd boinc Inorder for this to work the directory where boinc is stored must be in your path or you must use the complete path to boinc eg: /usr/boinc/boinc or if you cd to the boinc directory you could: cd ./boinc Naturally replace everything between the with what aplies for your setup. Hope this helps Keith J. Schultz schultzk@uni-trier.de |
N/A Send message Joined: 18 May 01 Posts: 3718 Credit: 93,649 RAC: 0 |
Oho! That makes sense... I don't think that the user permissions are going to be the reason - This happened even if I was root. I used to have to cd ~/.boinc ; ./boinc in the past. I'll try adding alii in /etc/bashrc and /etc/csh.*. |
Keith J. Schultz Send message Joined: 6 Apr 01 Posts: 49 Credit: 10,408 RAC: 0 |
Hi JP, MacOSX is basically BSD and /usr has the normal permission. As far as VT7 you are evedently running it with root rights and therefore it can have its processes put it files whereever it wants. I would suggest running it as a normal user belonging to a group with the appropiate permissions !! > Hello, friend ! > I don't understand why, as here, but with another OS, I runned first BOINC as > root in /boinc directory, and all the stuff was lying in this directory. Then > I tried to use it in an other directory (/home/godetj/ files/BOINC) as a > "normal" user (not the "super user" root)and all the files and subdirectories > are now in this directory. > Now BOINC is running as a background task in a special virtual console for > it (VT7) and the owner of the files and subdirectories generated by BOINC and > SETI client are now root, but are still remainning in this directory. > This is on a Linux machine (Slackware 10.0 with kernel 2.4.26). May be your > MacOS doesn't permit to a "normal" user to put files in /usr ? and force BOINC > to use the home directory of the user owning and running BOINC... > > Jean-Pierre > > Keith J. Schultz schultzk@uni-trier.de |
N/A Send message Joined: 18 May 01 Posts: 3718 Credit: 93,649 RAC: 0 |
I've futzed around with NetInfo a bit. Is there such a thing as an "everybody" group? I know there's a "nobody" group, so I'd assume that whoever worked the BSD users and groups would have thought of including an "everybody" group. Or will I have to create a "boinc" group? I want to make sure that even if the only person using the computer is an unpriviledged user (a guest, for instance), BOINC should be able to run its WUs without having to ask permission from an admin account. |
N/A Send message Joined: 18 May 01 Posts: 3718 Credit: 93,649 RAC: 0 |
Everything is set up perfectly... Except for one final problem. [grrrr!] Here's what I did: I downloaded BOINC 4.13, and cped it into /usr/local/bin where my other binaries will be. I then wrote setenv PATH "/bin:/sbin:/usr/bin:/usr/local/bin:/usr/sbin" in /etc/csh.login. I prefer bash, but I had a nagging feeling that the csh.login would be respected - And so far that seems to be the case. Next, I decided that /usr/local/share would be the appropriate place for the BOINC-related files, so I cd /usr/local/share-ed and executed boinc from there. Imagine my frustration when BOINC responded with 2004-12-04 00:48:28 [---] Another instance of BOINC is running. I've read ps ax thoroughly, and I can say with 100% certainty that BOINC is lying. What the hell is going on? |
N/A Send message Joined: 18 May 01 Posts: 3718 Credit: 93,649 RAC: 0 |
Never mind - I found the problem. /usr/local/share is not accessible to users! I can chown that away. Looks like the problem is solved, once and for all. Thanks to all of you for the help! :-) |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.