Posts by AtesComp

1) Message boards : Questions and problems : Updating BOINC on Ubuntu (Message 33818)
Posted 18 Jul 2010 by AtesComp
Post:
Oops,
For some reason the "service" command won't wait until it is finished before continuing to the next command. Even a "wait" command is ignored.
You might want to add a sleep command after the service stop so that it stops in time for the copies:
service boinc-client stop
sleep 1
Maybe doing a direct
/etc/init.d/boinc-client stop
would work.
2) Message boards : Questions and problems : Updating BOINC on Ubuntu (Message 33815)
Posted 18 Jul 2010 by AtesComp
Post:
There is a BOINC wiki for installing BOINC on Ubuntu:

http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Ubuntu

However, the repository package for BOINC is generally NOT up-to-date. I'd like to rectify that little problem by suggesting the following be added to the page:

10 Easy Steps to Update BOINC
To update BOINC you may do the following:

1. Download the latest BOINC software bundle from the BOINC web site for your flavor (32 or 64 bit) to your favorite download directory. This will be a ".sh" file.
Note: There is a notable problem using the 32 bit version on 64 bit platforms concerning message updates on the Messages tab.

2. In your download directory, change the ".sh" file properties to "executable" using your favorite method.

3. Run the ".sh" file, i.e.,
./boinc...sh
This should unpack the file and create a BOINC directory.

4. Create a BOINC Update script called "boinc_update.sh" in the download directory with the following commands in the file:
cp BOINC/boinc /usr/bin/boinc
cp BOINC/boinccmd /usr/bin/boinccmd
cp BOINC/boincmgr /usr/bin/boincmgr
cp BOINC/boincmgr.16x16.png /usr/share/pixmaps/boincmgr.16x16.png
cp BOINC/boincmgr.32x32.png /usr/share/pixmaps/boincmgr.32x32.png
cp BOINC/boincmgr.48x48.png /usr/share/pixmaps/boincmgr.48x48.png
cp BOINC/ca-bundle.crt /var/lib/boinc-client/ca-bundle.crt
cp BOINC/libcudart.so /var/lib/boinc-client/libcudart.so
Reuse this script whenever you want to update.

5. Make this new BOINC Update script executable.

6. Make sure your BOINC client service is stopped using your favorite method (I use BUM).

7. Make sure the BOINC Manager is closed.

8. Run the "boinc_update.sh" script as superuser, i.e.,
sudo ./boinc_update.sh"

9. Restart your BOINC client service.

10. Run the BOINC Manager to check your update.

Language Files:
The language files are not updated and I don't yet know where they should be placed, but I suspect they could be dumped in the /var/lib/boinc-client dir.

Run Files:
Apparently, the Ubuntu package does not contain the run... files, so they are ignored for updating purposes.

BOINC Client Service:

The service stop/start could be added to the script, but then it wouldn't be 10 Easy Steps, now would it.
Add:
service boinc-client stop
to the beginning of the script and
service boinc-client start
to the end of the script.
3) Message boards : BOINC Manager : 6.10.43 bug? entire message buffer being duplicated (Message 33814)
Posted 18 Jul 2010 by AtesComp
Post:
I just found out I had the same problem: 32 vs. 64 bit.
Thanks!

Also, I run Kubuntu and found the repository version is constantly behind. To update, I download BOINC, run the .sh file, and then run this little script:

cp BOINC/boinc /usr/bin/boinc
cp BOINC/boinccmd /usr/bin/boinccmd
cp BOINC/boincmgr /usr/bin/boincmgr
cp BOINC/boincmgr.16x16.png /usr/share/pixmaps/boincmgr.16x16.png
cp BOINC/boincmgr.32x32.png /usr/share/pixmaps/boincmgr.32x32.png
cp BOINC/boincmgr.48x48.png /usr/share/pixmaps/boincmgr.48x48.png
cp BOINC/ca-bundle.crt /var/lib/boinc-client/ca-bundle.crt
cp BOINC/libcudart.so /var/lib/boinc-client/libcudart.so


To run it (sudo), the client service must be stopped and the manager must be closed.

Maybe, this should be posted somewhere else?
Maybe, this could be included in the release?

Edit:
Don't know what to do about the language files.
Also, other files exist in the /etc/boinc-client dir.




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.