| Info | Message |
|---|---|
| 1) Message boards : BOINC Manager : Wishlist for Mac
Message 45445 Posted 26 Aug 2012 by aginghippie |
It was a user permissions issue. Resetting user permissions on the admin account (which is *supposed* to be the only BOINC user) set the BOINC daemon free. |
| 2) Message boards : BOINC Manager : Wishlist for Mac
Message 45400 Posted 22 Aug 2012 by aginghippie |
Another wrinkle is that I had to do a "dirty" install of 10.8 over 10.6. Maybe that's the problem.Remember that, since you are relocating the BOINC Data directory, you must create the symbolic link again each time you run the BOINC installer, as explained at the end of this section. This may also apply when upgrading the OS. I moved the data folder as the very last step. I deployed 20 machines. 19 of them are, in theory, exact clones of one machine (target disk mode is wonderful when one has an unreliable network that doesn't support netbooting). I used to expect that clones would behave the same, but they don't. Two of the 20 are behaving properly regarding BOINC. The other 18? Only FSM knows for sure why things don't work. I've never had good luck uninstalling and re-installing. I end up cloning from another machine, so that's pretty much where I start these days. When we used Radmind, we didn't have these problems. But my Radmind expert left... Turns out I've got to redo the machines with a clean install of 10.8, so I'll let you know. |
| 3) Message boards : BOINC Manager : Wishlist for Mac
Message 45389 Posted 21 Aug 2012 by aginghippie |
Hmmmmm.... I'm using the same settings I used with 10.6.8--and 10.7.x for that matter--where things worked swimmingly for lo these many years. That was BOINC 6.10.58. An added wrinkle is that because we Deep Freeze our lab Macs I moved the data folder to another partition so that work could be done between classes without thawing them. Another wrinkle is that I had to do a "dirty" install of 10.8 over 10.6. Maybe that's the problem. I appreciate your efforts in all this. |
| 4) Message boards : BOINC Manager : Wishlist for Mac
Message 45324 Posted 17 Aug 2012 by aginghippie |
I'm in the process of upgrading our Mac labs to OS 10.8. I'm running BOINC 7.0.31 (GUI) to go with the upgrade. While the log says BOINC is running as a daemon, no work is being done. Apple is notorious for tinkering under the OS hood without telling folks, so I'm wondering if there's a need for a new daemon script. Seems to me the same kind of thing happened when things switched to launchd. |
| 5) Message boards : BOINC client : BOINC daemon on Snow Leopard gives me headaches...
Message 40323 Posted 23 Sep 2011 by aginghippie |
Oh SUUUUUUUUURRRRRRRRRRRRE! I uninstalled Parallels 4.x and now-apparently--the daemon runs fine. Grrrrrrrrr...... Coulda. Woulda. Shoulda. |
| 6) Message boards : BOINC client : BOINC daemon on Snow Leopard gives me headaches...
Message 40318 Posted 23 Sep 2011 by aginghippie |
Sadly, we're using DeepFreeze in our Mac labs (my Radmind guru has departed for a full-time job). In order to preserve BOINC crunching--and user logs (the asl directory)--all the machines have an "invisible" partition called .stuff. I used the "move BOINC" instructions to move the data directory to .stuff and there was much automatic happy-happy-joy-joy crunching. 100% of the lab machines (circa 10.6.4) were configured successfully As I would apply system/security updates, many machines lost their BOINC daemon happiness. If I logged in manually, BOINC would start but not make a connection to the data directory on .stuff. If I manually quit BOINC and restarted it, crunching would resume. Console gives me this cryptic message: 9/23/11 8:53:59 AM com.apple.launchd.peruser.501[133] (edu.berkeley.boinc) Ignored this key: UserName 9/23/11 8:53:59 AM com.apple.launchd.peruser.501[133] (edu.berkeley.boinc) Ignored this key: GroupName The only other thing I can add is that if I turn off automatically start at login, the first manual start gives a boinc daemon error message. Dismissing the message, quitting and then restarting BOINC resumes the crunching. I'd *really* like to continue automatic BOINC crunching, but with such a high failure rate every time I run routine maintenance I may not be able to afford the time (once a machine fails, I have been unable to resurrect BOINC crunching) and human resources to do so until I can get Radmind back up and running. I wonder if *maybe* Apple was tinkering under the hood to prep for 10.7 and not telling people things again. I remember when launchd replacing cron caused issues which got fixed once people were aware of the need for a fix. I'm happy to supply any log data. Bear in mind I don't really know where all the stuff is hidden. |
| 7) Message boards : BOINC Manager : Wishlist for Mac
Message 31482 Posted 9 Mar 2010 by aginghippie |
It would be nice if someone took the time to make a nice, simple package installer for the Mac command line version. I'd be much happier running that version in our labs (100+ iMacs--mostly running 10.6.x), but the installation is pretty daunting under the best of circumstances. I really don't care about the screensaver side of things with the GUI app; I use it because the install is a piece of cake. Even this mere English and American Literature and Language major (Eastern Michigan University, 1976) can handle it with equanimity. Even with an experienced UNIX person walking me through the installation, all I could think was that all this command line hu-hu was exactly why I moved to the Mac 25 years ago. |
| 8) Message boards : BOINC Manager : 6.10.33 for the Mac--a nice touch with Charlie's daemon script
Message 31480 Posted 9 Mar 2010 by aginghippie |
I run 100+ Macs in our computer labs--all of them with the BOINC daemon. With every other release of BOINC, an update forced a reboot. Not that big of a deal, but a slight irritant. Multiply a slight irritant by 100+ and it can be aggravating. Not so with this release. Happy, happy, joy, joy! Nice work. A curiosity: The download page says 6.10.36. The software and documentation refers to 6.10.33. Yes, I also proofread menus at restaurants. It's a gift. It's a curse. |
| 9) Message boards : BOINC client : Leopard
Message 14742 Posted 8 Jan 2008 by aginghippie |
I wonder if maybe I need to do a clean install of BOINC. The machines with initial success were brand new; the machines that run all the time regardless of preferences have been around a while. I'm in the process of re-imaging anyway. I use Grid View to check out what's happening on my BOINC machines. Historically, when I would log in on machines running your script, all work would be suspended ("User logged in" type of message). Now, the older machines keep chunkin' away on the data with corresponding ticking of the clocks. The older machines are also the 1.83 Core Duos which are exhibiting interesting differences from the Core 2 Duos anyway. Maybe that's the difference as opposed to the Santa Rosa chipset... It's opening week for winter semester here, so I'm a bit busy with some other things. When it calms down (or during eyes of pedagogical hurricanes) I'll run the current set-up that works so well with the new machines on our two models of older machines with clean installs of BOINC. Please bear in mind that I'm an English major who left DOS.whatever in the mid-80s to groove on the Mac Plus--and I'm not a fan AT ALL of OS X. Yes, I was sad when the dinosaurs died. |
| 10) Message boards : BOINC client : Leopard
Message 14710 Posted 7 Jan 2008 by aginghippie |
Hmmmmm.... This combo appears to not work so well on pre-Santa Rosa chipset machines Intel iMacs. Runs all the time regardless of what I tell the local prefs to do. |
| 11) Message boards : BOINC client : Leopard
Message 14640 Posted 4 Jan 2008 by aginghippie |
Hey Charlie! I have the updated daemon script and 5.10.33 running in our brand-spankin'-new lab of 20" 2.4 GHz iMacs and things appear to working swimmingly. I expect to see some results turning up for these machines by noon EST. Thanks so much for the attention to this. For maintenance reasons we leav these machines on and I'd much rather they did something other than sit there. I've got 5 labs (100+ iMacs (1.83 GHz Core Duos, 2.0 GHz Core 2 Duos, and the aforementioned 2.4 machines)) AND official permission to run distributed computing projects in them. We're runnin' Tyger for production and Leper for internal testing (*mebbe* gonna deploy it Spring term). Happy to test things out anytime. |
| 12) Message boards : BOINC client : Leopard
Message 14548 Posted 27 Dec 2007 by aginghippie |
I've been running the BOINC daemon script for Macs in the computer labs I manage for many months. When we began to deploy Intel iMacs, I began seeing problems that didn't exist with our PPC machines; the PPC machines crunched happily away when no one was using them, and stopped when someone logged in--all the time peacefully co-existing with web-based preferences. Now, with both Leopard and Tiger machines, I have to set preferences to "Run Always" and "Network Always Available" in order to crunch units. This is causing a HUGE performance hit when students need to use the machines for assignments. I've heard rumors that a factor in all this is Apple's implementation of launchd to replace start-up items. I hope that someone can do something to return BOINC/Charlie's shell script to the days of yore, because it looks as if when classes resume January 8, my five labs of Intel iMacs won't be running BOINC anymore. |
Copyright © 2025 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.