I noticed when I run BOINC with Setiathome as an screensaver that when I try to shudown or reboot the system cannot kill the setiathome process. You need to kill the setiathome process in either "Activity Monitor" or command line in a terminal window.
This is new install of Leopard and updated to current updates (10.5.2) on a new hard drive on a PowerBook G4.
Has anyone else seen this?

---

Hi,

I'm going to need some information from you.
Are you running BOINC as a daemon? Are you running an optimized or otherwise 3rd party Seti application? Have you tried the stock application in that case?

You might want to try to upgrade to the latest 5.10 version first. It's 5.10.45, available from the Berkeley download site.

If you're running as a daemon, exiting BOINC Manager won't kill the client and thus not the application. You'll need to exit the daemon as well.
You may also want to set your preferences to run only when the user isn't active.

And lastly, there's of course the option to exit BOINC completely before shutting down.

---

I had a similar problem

Running Diskwarrior cured it.

---

Running Diskwarrior cured it.

How about running 'disk utility' or 'fsck'? Or the most likely solution, 'repair permissions'... ;)

(Personally, I'd reinstall Leopard before I spent a few hundred dollars on a disk repair tool.)

---

It may not be 1984 but George Orwell sure did see the future . . .

I noticed when I run BOINC with Setiathome as an screensaver that when I try to shudown or reboot the system cannot kill the setiathome process. You need to kill the setiathome process in either "Activity Monitor" or command line in a terminal window.
This is new install of Leopard and updated to current updates (10.5.2) on a new hard drive on a PowerBook G4.
Has anyone else seen this?

I have this same problem with 10.5 -- if Boinc is running and the S@H icon is active in the dock, it won't quit. Sometimes I can manually quit them. Sometimes the system dies. Boinc won't quit (not even kill -9) and the only way to power down is by holding the power button down.

---

Visit my website where you can see my Seti page, my blog, and anything else of interest. Write me at darsys at aol dot com if you want. My blog is at http;//www.darsys.net/quagmire.html

Boinc won't quit (not even kill -9)

Try it with a sudo tag... ;)

---

It may not be 1984 but George Orwell sure did see the future . . .

Running Diskwarrior cured it.

How about running 'disk utility' or 'fsck'? Or the most likely solution, 'repair permissions'... ;)

(Personally, I'd reinstall Leopard before I spent a few hundred dollars on a disk repair tool.)

If you do a Safe Boot, OS X will automatically run a number of repair functions (e.g., fsck, I believe) that might or might not resolve your problem. Do a Safe Boot by pressing and holding the SHIFT key when the restart chime sounds. After the restart is complete, do a normal restart.
<http://support.apple.com/kb/HT1564>

---

OS X will automatically run a number of repair functions (e.g., fsck, I believe)

Leopard keeps a record of fsck here: ~/Library/Logs/fsck_hfs.log ... ;)

---

It may not be 1984 but George Orwell sure did see the future . . .

Hi,

I'm going to need some information from you.
Are you running BOINC as a daemon? Are you running an optimized or otherwise 3rd party Seti application? Have you tried the stock application in that case?

You might want to try to upgrade to the latest 5.10 version first. It's 5.10.45, available from the Berkeley download site.

If you're running as a daemon, exiting BOINC Manager won't kill the client and thus not the application. You'll need to exit the daemon as well.
You may also want to set your preferences to run only when the user isn't active.

And lastly, there's of course the option to exit BOINC completely before shutting down.

Sorry for not replying earlier.
No, I'm not running a BONIC as a daemon and not running other optimized or 3rd party Seti application. This is a stock install from your website:
http://boinc.berkeley.edu/download.php
I haven't modified anything other than the view in BOINC and the Activity is set for "Run based on preferences" which should be running only as screen saver .

This what ps auwx |grep boinc shows:
boinc_project 56868 1.8 1.7 477016 53228 ?? SN 4:58AM 153:08.83 setiathome_5.28_i686-apple-darwin
boinc_project 56834 0.0 1.2 126576 39200 ?? SN 4:54AM 149:59.14 setiathome_5.28_i686-apple-darwin
boinc_master 200 0.0 0.1 2698544 4560 ?? S Wed02PM 2:29.85 /Applications/BOINCManager.app/Contents/Resources/boinc --redirectio --launched_by_manager

Again when this occurs I see is that setiathome_5.28_i686-apple-darwin application shows up in the Dock and I can see the application in "Force Quit" this when I can't shutdown or reboot my system normally unless I kill setiathome_5.28_i686-apple-darwin from Activity Monitor. Force Quit setiathome_5.28_i686-apple-darwin has no effect on this process so I have to use Activity Monitor kill the process.
My current version of BOINC is 6.2.14.
Right now I'm running Mac OS 10.5.4 and current updates from Apple.

---

I have the same Problem! Seti@Home will not allow my Mac to shutdown! I have to do a Force Quit every time! I just upgraded to the latest Bonic and I have all the latest Mac updates. I want to continue to use seti@home, but I have to get this fixed! Please help!

Kevin

---

Seti@Home will not allow my Mac to shutdown!

Why are you shutting down your mac? If you have a desktop, put it to sleep... If you have a laptop, close the lid... Hibernate mode uses very little power and your computer will thank you for using it... 'Uptime' is one of the best reasons to own a mac... ;)

(This mac-tip was brought to you by a fellow mac user, and endorsed by Apple.)

---

It may not be 1984 but George Orwell sure did see the future . . .