Message boards : BOINC client : Mac CLI Client and Remote Access
Message board moderation
Author | Message |
---|---|
Send message Joined: 27 Jan 06 Posts: 6 ![]() |
Hi, I have the Boinc Manager running successfully on one of my Mac's and also have the Boinc Client running successfully (an remotely) on my Linux Server (Ubuntu 6.06.1) but am not sure how to go about doing the same on another older PowerMac G4 I still use. I don't want to run the manager on the G4, just the command line client. I want it to be run at startup and be handled remotely. How do I go about doing that? I'm sure I can get the CLI version to work by moving it to /usr/bin/boinc/ (or somewhere like that) and running the scripts, but not sure what steps to take to access it remotely. I can't find the same gui_rpc_auth.cfg file that is on my linux box. Will this work on the G4 ? Thanks, Damon |
![]() Send message Joined: 29 Aug 05 Posts: 15632 ![]() |
You need the gui_rpc_auth.cfg on the computer that is just the host and a remote_hosts.cfg file on the computer that has the GUI. See http://boinc.berkeley.edu/trac/wiki/RpcAuth#remote_hosts and http://www.boinc-wiki.info/index.php?title=Remote_Hosts_File for more information on this. |
Send message Joined: 27 Jan 06 Posts: 6 ![]() |
Hello - thanks for the suggestions! I have it running smashingly -- wonderful. My last question is, though, how to make it run in the background on startup -- without having to start a terminal session. Is there an easy way to to do this ? Thanks, Damon |
![]() Send message Joined: 29 Aug 05 Posts: 15632 ![]() |
Not sure if you will see this as an easy option and I'm also not sure if it completely is what you look for. I am not that well versed on the Mac, but I know your OS is based on Unix. So see this write-up of how to make BOINC start as a daemon on Unix. As said, it may be that it's done totally different on the Macintosh, but it's the best advice I can give, until someone with Mac knowledge comes along. :-) |
Send message Joined: 27 Jan 06 Posts: 6 ![]() |
As said, it may be that it's done totally different on the Macintosh, but it's the best advice I can give, until someone with Mac knowledge comes along. :-) Hi thanks I will look at that -- I also found this which has a script that is supposed to do what I want ... And this works on one of my machines (the one with the Boinc Manager) but not on the other (the one with the command line client). When I look at the scripts output (creating the startupitems folder and script) they look identical (except for the locations of the executables). But one is working and other is not ... I don't know where to find the startupitems.log ... or see what error messages are being thrown at startup either ... to see what the problem is. It might be something as simple as permissions but I don't know enough about Macs either to sort it out. Is working on one machine, though ... so that is something ... |
![]() ![]() Send message Joined: 30 Oct 05 Posts: 1239 ![]() |
That link would be... http://boinc.berkeley.edu/mac_admin_tools.php Edit... I know less than nothing about Macs, but could you use spotlight to search for the log? Kathryn :o) |
![]() Send message Joined: 12 Feb 06 Posts: 232 ![]() |
Not sure if you will see this as an easy option and I'm also not sure if it completely is what you look for. I am not that well versed on the Mac, but I know your OS is based on Unix. So see this write-up of how to make BOINC start as a daemon on Unix. It's not totally different. As on Linux you have a script which is run when the system boots or at shutdown. It takes the single command line argument "start" or "stop". But on the Mac is lives in /Library/StartupItems, and the internals are different on Mac compared to Linux. -- Eric Myers "Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats |
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.