Like I said, it's not mine. I really can't take any credit for it. But I will forward it to Paul anyway.

---

7,049 S@H Classic Credits

Here is how I do it.

[font='courier,courier new'] ! I think you should give Paul a copy of your how-to for the Wiki.[/font]

---

Ken,

Glad to hear that it's working well for you, but don't give me any credit for this. :) I write web scripts not bash scripts.

I've not had any problems with it on Mandriva (Mandrake) or Fedora except for the occasional glitch where the lockfile is not deleted on shutdown. It's a bit of a pain to su and delete it manually but it hardly ever happens so it's not a big deal.

I've not seen anything like you describe so I'm not sure what that was about. If you were only looking at the seti app and not boinc in top it may be that boinc was doing it's CPU benchmarking at the time. That's about all I can offer without knowing more.

---

7,049 S@H Classic Credits

And just in case there wasn't enough suggestions in this thread... Here is how I do it. This script has worked on Fedora, Mandriva, and other distibutions (Some exclusions may apply, see store for details).

I used to just call the BOINC daemon from rc.local but I dropped that in favor of this approach. Running it under a different user also makes it very easy to check on things [$ top -u boinc] and start and stop the service if I need to [# service boinc start|stop|restart|status].

Ampoliros

Cheers! I tried those script instructions you posted on RH8 (I know it's ancient!), and that script works a treat, once the user name is created properly and permissions sorted (goodbye two trashed workunits :-0 ), it even deletes the lockfile afterwards, however, I'm not sure this is a 'one off', but, the first time I actually rebooted, shortly after doing the setup, seti@home wasn't getting any CPU time, TOP showed it just sitting there running at zero!
I stopped boinc, that didn't stop seti@home, so I killed it, then restarted the boinc service. All is now well, boinc is running at almost zero cpu, and seti@home is near 99%, and neatly steps out of the way when required.
I haven't tried another reboot yet, but, is it likely to repeat the above issue?
I'll try another reboot once/if it crunches a few more wu's.

Wow, my RAC actually went up a bit today, there must be something wrong :-)

TTFN, Ken Phillips

---

Ken Phillips

BOINC question? Look here



"The beginning is the most important part of the work." - Plato

And just in case there wasn't enough suggestions in this thread... Here is how I do it. This script has worked on Fedora, Mandriva, and other distibutions (Some exclusions may apply, see store for details).

I used to just call the BOINC daemon from rc.local but I dropped that in favor of this approach. Running it under a different user also makes it very easy to check on things [$ top -u boinc] and start and stop the service if I need to [# service boinc start|stop|restart|status].

---

7,049 S@H Classic Credits

[font='courier,courier new']That's pretty much it. I prefer the ~/.bash_profile method (as shown below) but the idea is that BOINC should be the last call in init, but before the login app is called.

Here's how I do it:
# ~/.bash_profile
alias boinc="cd /Library/Application\\ Support/BOINC\\ Data/; (/Applications/BOINC\\ Menubar.app/Contents/Resources/./boinc &); cd $OWD;"
# Some more junk here...
boinc
# End of file

Depending on what you're running, you'll hafta adjust the execution line.[/font]

---

So, what your saying is, put:
/boinc/folder/destination/./boinc -return_results_immediately at the end of /etc/rc.d/rc.local???? (running Mandriva 2k5 LE)


I been trying to figure this out also, I would like boinc to start on my P4, as all it does is crunch, that way, when the wife trips a breaker it doesnt have to wait till I get home from work......heh

Hi!
I put this into my rc.local:

echo "cd /home/boinc;./do_boinc >>b.log 2>&1 &" |su - boinc

do_boinc is shell script to start boinc, b.log records all messages.

Boinc runs as user boinc, of course.

73
Iztok

So, what your saying is, put:
/boinc/folder/destination/./boinc -return_results_immediately at the end of /etc/rc.d/rc.local???? (running Mandriva 2k5 LE)


I been trying to figure this out also, I would like boinc to start on my P4, as all it does is crunch, that way, when the wife trips a breaker it doesnt have to wait till I get home from work......heh

---

They have lost me to MiniZiper. Maybe the easy way is to just leave your machine running.

---

[font='courier,courier new']"init" usually means initialization, and ".d" usually means daemon - What used to be called "TSR"s in DOS ("INIT" or "Extensions" in Mac OS). When Linux boots up, it reads its init.d file to find out what to do, in the same way that DOS ran autoexec.bat. Some distros execute rc; others, /boot. Ideally, you'd add your ./boinc line at the end of init.d, and it would work.

Another possibility is to add it to your own .login (or .bash_profile) file. This is easier to recover from if the line doesn't work, but you'd have to login to your user account (on your computer) in order to get started.

Either way, "Hay que ser Mandraque..." !-P[/font]

---

Make that BOINC starts automatically wen Linux starts ? I got Mandriva Linux BETA 2...Please help!

One of the neat (and/or frustrating) things about Linux is that there are a bunch of ways of accomplising the same thing. In my case seti/boinc runs as a user only. While the init.d script will work for that, we only have system related items start up that way on the seti machine. The quick and dirty way we're starting it is via the @reboot instruction in crontab. There's all sorts of pros and cons on how you do it. In crontab, the user that is the 'seti user' has @reboot /home/scale1/BOINC/boinc as the first line. When the system reboots (which is seldom) boinc starts up and runs. If we want to shut it down (again, seldom) we kill boinc and the setiathome with kill and pidof.
Bet you're REAL confused now, huh? :)

Well, I have to say that I'm a "noob" with linux.. so I have no clue what the script is all about... hehe...sorry

---

Please have a look at the init.d script in this message:
Linux init.d Script

This might get you started.

---

This is the voice of world control. I bring you peace. It may be the peace of plenty and content or the peace of unburied dead. The choice is yours.

Make that BOINC starts automatically wen Linux starts ? I got Mandriva Linux BETA 2...

Please help!

---