What is proper boinc client program to run when Linux system boots?

Message boards : BOINC client : What is proper boinc client program to run when Linux system boots?
Message board moderation

To post messages, you must log in.

AuthorMessage
Jean-David

Send message
Joined: 19 Dec 05
Posts: 89
United States
Message 11539 - Posted: 6 Jul 2007, 16:23:48 UTC

I have Eric Myers boink start script that goes in /etc/rc.d/init.d. But it needs configuration, and his script wants the name of the boinc client program. He calls his /usr/bin/boinc_client. But when I install boinc and run it, it puts all that stuff in /home/boinc where I want it. I can run it from there by running BOINC/run_client.

Now the runnable stuff in /home/boinc/BOINC includes:
boinc
boinc_cmd
run_client

Which one should I use for his script? When he gets around to it, he is in /home/boinc
and does
su boinc -c "$BOINCEXE $BOINCOPTS" >>$LOGFILE 2>>ERRORLOG &

The question is, which of the above three should I put in there?
ID: 11539 · Report as offensive
Eric Myers
Avatar

Send message
Joined: 12 Feb 06
Posts: 232
United States
Message 11540 - Posted: 6 Jul 2007, 16:34:08 UTC - in response to Message 11539.  
Last modified: 6 Jul 2007, 16:35:44 UTC

I have Eric Myers boink start script that goes in /etc/rc.d/init.d. But it needs configuration, and his script wants the name of the boinc client program. He calls his /usr/bin/boinc_client. But when I install boinc and run it, it puts all that stuff in /home/boinc where I want it. I can run it from there by running BOINC/run_client.

Now the runnable stuff in /home/boinc/BOINC includes:
boinc
boinc_cmd
run_client

Which one should I use for his script? When he gets around to it, he is in /home/boinc
and does
su boinc -c "$BOINCEXE $BOINCOPTS" >>$LOGFILE 2>>ERRORLOG &

The question is, which of the above three should I put in there?


The "boinc" file is the one I call the boinc_client.

I intended the name change to reduce confusion, not add to it. Sorry.

As you'll see if you look in it, run_client is just a short script to run "boinc" in the directory in which it was originally unpacked.

And boinc_cmd lets you give "commands" to the client while it is running.

If you've not seen the documentation that goes with the script, it's at http://www.spy-hill.net/~myers/help/boinc/unix.html. You will see there where I suggest copying the "boinc" file to be "boinc_client". But any suggestions on how to make this page clearer are most welcome.

-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats
ID: 11540 · Report as offensive
Jean-David

Send message
Joined: 19 Dec 05
Posts: 89
United States
Message 11542 - Posted: 6 Jul 2007, 17:06:09 UTC - in response to Message 11540.  

I have Eric Myers boink start script that goes in /etc/rc.d/init.d. But it needs configuration, and his script wants the name of the boinc client program. He calls his /usr/bin/boinc_client. But when I install boinc and run it, it puts all that stuff in /home/boinc where I want it. I can run it from there by running BOINC/run_client.

Now the runnable stuff in /home/boinc/BOINC includes:
boinc
boinc_cmd
run_client

Which one should I use for his script? When he gets around to it, he is in /home/boinc
and does
su boinc -c "$BOINCEXE $BOINCOPTS" >>$LOGFILE 2>>ERRORLOG &

The question is, which of the above three should I put in there?


The "boinc" file is the one I call the boinc_client.

I intended the name change to reduce confusion, not add to it. Sorry.

As you'll see if you look in it, run_client is just a short script to run "boinc" in the directory in which it was originally unpacked.

And boinc_cmd lets you give "commands" to the client while it is running.

If you've not seen the documentation that goes with the script, it's at http://www.spy-hill.net/~myers/help/boinc/unix.html. You will see there where I suggest copying the "boinc" file to be "boinc_client". But any suggestions on how to make this page clearer are most welcome.



Thank you. But I believe I want run_cmd after reading what it does.
Your script puts us in $BOINCDIR which, for me, is /home/boinc.
Now it is important to run the boinc client program in the directory where it is, or it gets confused about what is what, by far! Now all the run_cmd does is

cd "/home/boinc/BOINC" && exec ./boinc $@

which gets you into that directory and runs it.

I am not sure how to make your page more clear, but I am about to try it.

(I was using an old version of your script that I had to modify and wanted to start over clean.)
ID: 11542 · Report as offensive
Eric Myers
Avatar

Send message
Joined: 12 Feb 06
Posts: 232
United States
Message 11543 - Posted: 6 Jul 2007, 18:01:07 UTC - in response to Message 11542.  


Now it is important to run the boinc client program in the directory where it is, or it gets confused about what is what, by far!

I think that used to be the case, but I just tested it with 5.8.16 on Fedora Core 5 and it works as I expected. That is, you can cd to /home/boinc and then run /usr/local/bin/boinc_client and all the log files and other files it uses are under the CWD, ie. /home/boinc.

I just updated the script so that it should work with Debian's /etc/default/,
and to add a link to the documentation. And I made some small tweaks to the documentation page.


-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats
ID: 11543 · Report as offensive
Eric Myers
Avatar

Send message
Joined: 12 Feb 06
Posts: 232
United States
Message 11563 - Posted: 9 Jul 2007, 16:56:58 UTC - in response to Message 11542.  


Now it is important to run the boinc client program in the directory where it is,


Actually, I've done some more experimenting, and I find that you want to launch the client from the top level working directory (eg /home/boinc), which the init script does, but the real issue is where you are when you launch the manager.

If you launch the manager from the same directory then all is well.

If you launch it from anywhere else then it can't find gui_rpc_auth.cfg and complains, though you can get around this by pulling down "Advanced -> Select computer..." and using "localhost" as the computer name and the password found in gui_rpc_auth.cfg (which you can change if you want).

That is a little complicated, so a workaround is to copy just gui_rpc_auth.cfg to your home directory, then launch the manager there.

I think it would be easier and more consitent with how other things in Unix work if the manager would also look for the file in your $HOME directory (or perhaps a similar file with a different name, beginning with a dot).

-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats
ID: 11563 · Report as offensive
Jean-David

Send message
Joined: 19 Dec 05
Posts: 89
United States
Message 11565 - Posted: 9 Jul 2007, 22:06:48 UTC - in response to Message 11542.  

I have Eric Myers boink start script that goes in /etc/rc.d/init.d. But it needs configuration, and his script wants the name of the boinc client program. He calls his /usr/bin/boinc_client. But when I install boinc and run it, it puts all that stuff in /home/boinc where I want it. I can run it from there by running BOINC/run_client.

Now the runnable stuff in /home/boinc/BOINC includes:
boinc
boinc_cmd
run_client

Which one should I use for his script? When he gets around to it, he is in /home/boinc
and does
su boinc -c "$BOINCEXE $BOINCOPTS" >>$LOGFILE 2>>ERRORLOG &

The question is, which of the above three should I put in there?


The "boinc" file is the one I call the boinc_client.

I intended the name change to reduce confusion, not add to it. Sorry.

As you'll see if you look in it, run_client is just a short script to run "boinc" in the directory in which it was originally unpacked.

And boinc_cmd lets you give "commands" to the client while it is running.

If you've not seen the documentation that goes with the script, it's at http://www.spy-hill.net/~myers/help/boinc/unix.html. You will see there where I suggest copying the "boinc" file to be "boinc_client". But any suggestions on how to make this page clearer are most welcome.



Thank you. But I believe I want run_cmd after reading what it does.
Your script puts us in $BOINCDIR which, for me, is /home/boinc.
Now it is important to run the boinc client program in the directory where it is, or it gets confused about what is what, by far! Now all the run_cmd does is

cd "/home/boinc/BOINC" && exec ./boinc $@

which gets you into that directory and runs it.

I am not sure how to make your page more clear, but I am about to try it.

(I was using an old version of your script that I had to modify and wanted to start over clean.)


I notice if I start boinc with this script, it does start. But it gives an error return.

And when I try to make it stop boinc, it says it is not running. I will look at it some more later.
ID: 11565 · Report as offensive
Eric Myers
Avatar

Send message
Joined: 12 Feb 06
Posts: 232
United States
Message 11568 - Posted: 9 Jul 2007, 23:30:46 UTC - in response to Message 11565.  

I notice if I start boinc with this script, it does start. But it gives an error return.

And when I try to make it stop boinc, it says it is not running. I will look at it some more later.


What flavor of Linux? Did you run it as root or as a normal user? Let me know if you find the problem.

-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats
ID: 11568 · Report as offensive
Jean-David

Send message
Joined: 19 Dec 05
Posts: 89
United States
Message 11570 - Posted: 10 Jul 2007, 0:43:54 UTC - in response to Message 11568.  

I notice if I start boinc with this script, it does start. But it gives an error return.

And when I try to make it stop boinc, it says it is not running. I will look at it some more later.


What flavor of Linux? Did you run it as root or as a normal user? Let me know if you find the problem.


I just started running Red Hat Enterprise Linux 5; I was running RHEL3 since early 2004.

I "fixed" your script by changing it where it enters start and stop, where it does a cd $BOINCDIR to go to $BOINCDIR/BOINC . I have not studied it sufficiently to see if I could just define BOINCDIR as /home/boinc/BOINC in /etc/sysconfig/boinc instead. I believe I can, but I will try it another time.
ID: 11570 · Report as offensive

Message boards : BOINC client : What is proper boinc client program to run when Linux system boots?

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.