(old)Puppy Linux Discussion Forum

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

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

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

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.

Nipar101 wrote: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.

oops, it was only one line, fixed typo.

Nipar101 wrote: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.

hmm, make sure you got at least 250mb of free space, or it will give errors.

Nipar101 wrote: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.

in rc.local the client starts at boot, without typing anything extra.

Nipar101 wrote: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.

Try uninstalling BOINC and deleting the folder /usr/lib/BOINC and reinstall BOINC.

I use this sript in init.d to start and stop Boinc.
Copy the script to a new file in /etc/init.d/. Change the paths so that they corresponds to your system and change the file to executable. This way your Boinc install will start automatically at startup.

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

Nipar101 wrote: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

yup, just one line is needed in rc.local

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

ZAPPDOG wrote: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

oops, that was using the coral cache mirror which must be down? its now fixed to use caneri's server. Thanks for the alt. link.

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

legendofthor wrote: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

howdy
that is an error that i have not seen. I have been running boinc in puppy for a couple of years. If you use the .pet listed above then running it in terminal isn't necessary. It runs from a gui listed in your menu under "Utility". it looks and acts the same as the windows version. And I have never had errors of any kind.
if you aren't using the .pet then check out the second post of mine here
http://teamcanada.freeforums.org/puppy- ... -t203.html
It uses the older style installation.
And should you need any help, please PM me there or here or Uncle Zaps forum in my sig.. I will gladly help.

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


SWEET!!!!!!!!

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.

gday
after much digging I have found out what is causing this..
my apologies to the community...
It not my computer; nor set-up; (ZAPPDOG - I use the Terminal just to check to see if all libraries, etc work); nor the personal file space; nor my dodgy typing thumbs....
apparently its my ISP and a number of the Australian community have experienced this same issues with said ISP - neither is help given by said ISP...
I am changing ISP in a couple of months - so will try BOINC then... <Sigh!>
BAH! too many hours wasted!!!
cheers
Martin

BOINC updated to 6.4.5

Please Reboot after installing.

Hey All
A new thread for Boincin' Puppies.
Drop by and say Howdy and take part in the poll.
http://unclezapaudiozap.phpbb3now.com/v ... 82&start=0

Member of Team Canada
http://teamcanada.freeforums.org/index.php

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

boinc-6.4.5.pet
md5sum

I want to download the boinc pet but it is asking for a username and password. Am I doing something stupid or is there something wrong with the link?

as far as i know
user: puppy
password: linux