Date: Tue, 20 Dec 2005 09:59:57 -0500 From: "J.R. Oldroyd" <fbsd@opal.com> To: Kent Stewart <kstewart@owt.com> Cc: Edwin Groothuis <edwin@mavetju.org>, freebsd-ports@freebsd.org Subject: Re: boinc-setiathome on 6.0 Message-ID: <20051220145957.GL11719@linwhf.opal.com> In-Reply-To: <200512200438.08552.kstewart@owt.com> References: <20051220103850.GA28819@k7.mavetju> <200512200438.08552.kstewart@owt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 20, 04:38, Kent Stewart wrote: > On Tuesday 20 December 2005 02:38 am, Edwin Groothuis wrote: > > I get: > > > > Message from server: platform 'i386-portbld-freebsd6.0' not > > found. > > > > Does anybody have hints on how to overcome this problem? > > Make sure you have a clean build of both and then reset and update your > project. It always took off after that. > I've had this question a few times, so here are the details... Boinc is a tool that downloads applications and then datasets, runs the applications on that data, and then uploads the results. For boinc to be able to download an application, a binary must be available on the server for your architecture/OS combination. However, since FreeBSD isn't as popular as other OSs, most application servers don't support downloadable binaries for FreeBSD. The message you saw tells you that you have attempted to download a binary for an application for i386/freebsd6.0 but this was not available. The boinc-setiathome port compiles the SETI application from source installs it locally and also installs the file ~boinc/projects/setiathome.berkeley.edu/app_info.xml which is used by boinc to find the installed SETI application which boinc will then use, rather than trying to download a binary from the SETI server. Since you have attempted to download a binary, this means that something isn't installed correctly. Either the app_info.xml file is missing, or the user "boinc" is not set up properly or the ~boinc directory or one of the subdirs has a permissions problem. If deinstalling and reinstalling both ports doesn't fix things, check that the boinc user and ~boinc directory permissions are OK as these are created when the ports are first installed, but not changed on later installs. The boinc user can have any user ID, the ~boinc dir (default /var/db/boinc, but can be anywhere) and subdirs must match the user ID and be at least rwx for the boinc user. Oh, and when you start boinc, you must use the bin/boinc script or the rc.d/boinc script, both of which su to the boinc user before starting things up. If you run lib/boinc/boinc-client directly and you are not su'd to the user boinc, things probably won't work properly either. -jr
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051220145957.GL11719>