Message boards : Questions and problems : Problems with BOINC 6.10.17 on Mac OS X 10.6.1
Message board moderation
Author | Message |
---|---|
Send message Joined: 30 Oct 09 Posts: 13 ![]() |
Hi, From my administrative user id I was trying to use AddRemoveUser command line tool to allow a non-privledged user to run BOINC. The tool crashed with a EXC_BAD_ACCESS (SIGBUS) exception type (crash report provided upon request). So I tried reinstalling BOINC 6.10.17 and am now getting the following Console message: 11/9/09 3:00:56 PM com.apple.launchd.peruser.501[181] ([0x0-0x18018].edu.berkeley.boinc.Installer[238]) Exited with exit code: 246 So now I can only run BOINC Manager on my administrator user id, which is not my non-privledged standard user id where I normally work. Can someone tell me how to get out of this Catch 22 circle so I can allow my non-administrative (ie standard Mac OS X account) user id run BOINC? Thanks Craig Dudley |
Send message Joined: 30 Oct 09 Posts: 13 ![]() |
Hi, Well, it looks like the AddRemoveUser command line tool actually worked because my standard, non-privledged account now can run BOINC without a popup window stating I need to contact my BOINC Administrator to add my user id to the list of authorized users for running BOINC. So I guess I am down to the Installer "Exited with Code: 246" problem. Craig Dudley |
Send message Joined: 17 Jul 06 Posts: 287 ![]() |
Hello Craig, What version of OS X are you running? Is your Mac PowerPC or Intel? Other than the console message, did the installer itself indicate that it had a problem? Did the installer ask whether to allow non-administrative users to run and control BOINC? If so, did you answer Yes? Please do send the crash dump from AddRemoveUser. Charlie Fenton BOINC / SETI@home Macintosh & Windows Programmer |
Send message Joined: 30 Oct 09 Posts: 13 ![]() |
Hi, As I said in my Subject line, I am running 10.6.1 and as such, running on a quad processor Intel Mac Pro. I didn't see any other indication that the installer had a problem other than it didn't start when double clicked. When I originally installed BOINC 6.10.17, I diod answer Yes to the question of allowing non-administrative users to run and control BOINC. Now not to completely screw things up, on another system I installed Mac OS X 10.6.2 and then installed BOINC 6.10.17 and answered Yes to the non-administrative user question.. Then I downloaded AddRemoveUser and ran it on a Terminal command line and did not have a crash. So maybe something got fixed in 10.6.2. Where do you want me to send the crash report? Thanks Craig Dudley |
Send message Joined: 17 Jul 06 Posts: 287 ![]() |
Where do you want me to send the crash report? I only need the backtrace portion (the part before the "Thread State" and "Binary Images" sections. It should only be a couple dozen lines or less. Please just paste it into a message here. I didn't see any other indication that the installer had a problem other than it didn't start when double clicked. Sorry, I'm a bit unclear here: what didn't start when double-clicked? Are you saying BOINC wouldn't run, or that the installer wouldn't start? I didn't see any mention of that in your earlier posts. Every user can always to launch BOINC. The only difference if a particular user is not authorized to run BOINC is that BOINC will display a message saying that user is not authorized and then quit. I installed Mac OS X 10.6.2 and then installed BOINC 6.10.17 and answered Yes to the non-administrative user question.. Then I downloaded AddRemoveUser and ran it on a Terminal command line and did not have a crash. So maybe something got fixed in 10.6.2. I'm a bit puzzled. Why did you also run AddRemoveUser? Answering Yes to the installer question should have been enough to allow all users to run BOINC. Did you try running BOINC after installing and found that had not worked? Charlie Fenton BOINC / SETI@home Macintosh & Windows Programmer |
Send message Joined: 30 Oct 09 Posts: 13 ![]() |
I didn't see any other indication that the installer had a problem other than it didn't start when double clicked. Sorry, I'm a bit unclear here: what didn't start when double-clicked? Are you saying BOINC wouldn't run, or that the installer wouldn't start? I didn't see any mention of that in your earlier posts. *****What didn't start was BOINC Installer***** Every user can always to launch BOINC. The only difference if a particular user is not authorized to run BOINC is that BOINC will display a message saying that user is not authorized and then quit. I installed Mac OS X 10.6.2 and then installed BOINC 6.10.17 and answered Yes to the non-administrative user question.. Then I downloaded AddRemoveUser and ran it on a Terminal command line and did not have a crash. So maybe something got fixed in 10.6.2.
*****I thought you need to run AddRemoveUser to add the specific users ids of those non-administrative users allowed to run BOINC Manager. I didn't know answering Yes to the installer question was the only step needed for non-administrative users to run BOINC Manager.***** [/quote] |
Send message Joined: 17 Jul 06 Posts: 287 ![]() |
Craig: Thanks for your help. I think I've found the reasons for both problems. They should be fixed in the next release. Charlie Fenton BOINC / SETI@home Macintosh & Windows Programmer |
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.