| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Filipe Borges
Cruncher Joined: Aug 8, 2006 Post Count: 33 Status: Offline Project Badges:
|
Hi. I'd like to know if someone here has ever installed BOINC as a service in linux. It really bothers me having to open the terminal and type the comands each time I restart my computer, so I would like to know if it's possible having BOINC starting automatically when I turn on the machine. I deeply searched the forum, but I've found nothing about it...
BTW, I'm sorry for the bad english: I'm Brazilian and I'm not such a got speaker yet. Best wishes, Filipe Borges |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Instructions for that are here . For wget use, the init.d script is at http://www.spy-hill.net/~myers/help/boinc/init.d/boinc . My version of instructions are below, which may be helpful suplemental to or instead of those on that page.
----------------------------------------Download the file to /etc/init.d or your equivalent directory. For it to work, you may need to change the first line to read '#/bin/bash' and set the variables to appropriate values: BOINCUSER is, I believe, the user name of the owner of your boinc directory. BOINCDIR is the location of your BOINC directory (e.g., /home/user/boinc) BUILD_ARCH is... I forget, but it should be set to a reasonable default or explain further in the script's comments BOINCEXE is the location of the program you run to run boinc. It needs to be in $PATH, so if you downloaded the program from the website instead of installing it from a package manager you might need to create a script in /usr/bin (or equivalent) to start boinc, and put the name of this script under BOINCEXE. An easy command for this is: "sudo echo -e #/bin/bash\ncd /home/user/boinc\n./boinc >> /usr/bin/boinc ; sudo chmod +x /usr/bin/boinc" ...replacing "/home/user/boinc" with your BOINC directory, of course. Then set BOINCEXE to "boinc" EDIT: If I recall correctly, you can't just use the path of the program (e.g., /home/user/boinc/boinc) for this because it uses the value of this variable to check whether the boinc process is already running) Next, you will need to configure it to start when you boot the computer. I usually use sysv-rc-conf for messing with services; if you do too, start it, scroll down to the new boinc entry, select the collumn for your default runlevel/s and press space. This is what will make the service start when you boot. I think I had to do a little extra editing to actually get it to work... something about lockfiles. When you run the client manually, it makes a lockfile which isn't removed when the client exits; so you might need to either remove it manually before starting the service the first time, or edit the script to ignore it. I can probably be a little more helpful once I get home. [Edit 1 times, last edit by Former Member at Sep 26, 2007 3:57:10 AM] |
||
|
|
Hanski
Senior Cruncher Finland Joined: Nov 14, 2005 Post Count: 157 Status: Offline Project Badges:
|
I made it run as service much easier way. I just add a line
----------------------------------------/path_to_the_directory/BOINC/run_client &in the /etc/rc.local -file.
<><
|
||
|
|
Filipe Borges
Cruncher Joined: Aug 8, 2006 Post Count: 33 Status: Offline Project Badges:
|
Thanks for your help guys! I took your tips and it's working nicely here, I really appreciate your time!
Best wishes, Filipe Borges |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
FWIW, I used the instructions on Eric's page and was able to successfully get it to work on FC7. I'm very much a noob (but making progress).
I think I had to do a little extra editing to actually get it to work... something about lockfiles. When you run the client manually, it makes a lockfile which isn't removed when the client exits; so you might need to either remove it manually before starting the service the first time, or edit the script to ignore it. I can probably be a little more helpful once I get home. I ran into the lockfile issues. I asked Eric about them. He told me to run the script with status as the argument to see what was going on. If you get something like "BOINC daemon stopped by lockfile exists" rerun the script with stop and then start. So basically, # /etc/init.d/boinc status <enter> and see what it says. If the daemon isn't running then, # /etc/init.d/boinc stop <enter> # /etc/init.d/boinc start <enter> HTH |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Too easy, Hans. :)
KSMarksPsych: That's neat. I solved it by commenting out the lines that checked for the lockfile (148-150ish), but that would probably work better.... Sure enough, I uncommented said lines and it works normally. Which probably means that the easiest solution would be to just remove the lockfile before the first run. ;p |
||
|
|
|