Puppy Linux Discussion Forum

[Wolf Pup]

Note: Needs around 250mb of free space to work.

Join Puppy Team: http://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=C2BK9RFBQ1

boinc-6.10.44.pet
md5sum

[Lobster]

http://boinc.berkeley.edu/

[Evil20071]

Cool. Now I can get doing SETI @Home again.

[ZAPPDOG]

Very cool Wolf Pup !
As a member of Team Canada http://teamcanada.freeforums.org/index.php I have been promoting puppy in their forum and its nice to see a simple alternative to the old .sh file.
It works great.
Many thanks

[Nipar101]

Bear with me, fairly new to linux, and Puppy Linux is a great welcome surprise.

I need some help though with the following:

Issues that need resolving regarding Puppy 4.00 and Boinc:
(Wolf Pup's boinc-6.2.15.pet )

1. Instructions for launching boinc client at startup via rc.local dont work.
Boot hangs at rc.local and exits to bash prompt.
The text file included in the pet file mentions 2 lines need to be
added and shows only one.

2. After puppy loads to desktop, running boinc manager loads the application and
starts the client. Exit the manager, and the client exits also without saving current
state of task. Upon restarting the computer and relaunching boinc manager, the client
reports "computation error" of the current task and moves on to start a new task.

3. Running "/usr/lib/BOINC/run_client" in rxvt console after the desktop loads starts the
client just fine. When you run boinc manager everthing seems fine, exit boinc manager and
the client remains running. That's good. Close the rxvt console running the client
(window close), exits the client without first saving data and state to harddrive
resulting in "computation error" on next client start.
However, pressing "ctrl+c" exits the client properly.

4. Restarting the computer with boinc client running causes the client to be killed by sigterm without client state and data first being written to harddrive. Again, resulting in task corruption.

Conclusion: a nice way of starting and shutting down boinc client properly is needed.


I am using Puppy 4.0 in the hopes of being able to setup some computers to autorun
BOINC without monitors, keyboards, or mice. The way things work now, I cannot leave them
unattended and any interuption in power would just make a mess of things.

Hope you can help. Thanks in advance.

[Wolf Pup]

[Anti]

I use this sript in init.d to start and stop Boinc.

[Nipar101]

Thanks so much for the info. everything working nice now.
I did make a mistake not putting the "&" after the line for boinc, fixed that.
the script provided looks good, will give a go.

wolfpup, is it only one line from the text file required?

Thanks so much for the quick reponse

[Wolf Pup]

[ZAPPDOG]

Hey Wolfpup
Just to let you all know, that download link is not up right now. I've tried it a few times this weekend. Eric is still working on that server.
I have it here through MSN's Skydrive
boinc-6.2.15.pet

[Wolf Pup]

[legendofthor]

gday
just started using boinc today - seti and climateprediction - program appears to work ok except when i ask for a an update; as the projects both have
"scheduler request pending" .... this comes out in the messages
scheduler request failed: error 417
any ideas?
NB: no errors appeared except that one when running in Terminal

[ZAPPDOG]

[puppyluvr]

Wolf Pup,
Thanks....Been a seti@home member since 2002, nice to run it in Puppy. Works great!!!
.. Jay..


SWEET!!!!!!!!

[ndujoe1]

When I had errors, Wolf_pup suggested that I increase the Personal file size. That did the trick and Bionic has been working very well since then.