From owner-freebsd-ports@FreeBSD.ORG Mon Jun 14 11:10:42 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76CB416A4CE for ; Mon, 14 Jun 2004 11:10:42 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id F21D643D45 for ; Mon, 14 Jun 2004 11:10:41 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id i5EBATco000950; Mon, 14 Jun 2004 04:10:30 -0700 From: Kent Stewart To: freebsd-ports@freebsd.org Date: Mon, 14 Jun 2004 04:10:32 -0700 User-Agent: KMail/1.6.2 References: <001501c451fc$1479edc0$7890a8c0@dyndns.org> In-Reply-To: <001501c451fc$1479edc0$7890a8c0@dyndns.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406140410.32197.kstewart@owt.com> cc: rcraig@fsegura.com cc: Cyrille Lefevre cc: 'Edwin Groothuis' Subject: Re: SETIATHOME PORT X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2004 11:10:42 -0000 On Monday 14 June 2004 03:40 am, Cyrille Lefevre wrote: > "Rob Craig" wrote: > > Hello all, > > > > Had had loads of problems over the last few days. Looks like the > > problem is related to the work unit. Same symptoms as before. TOP > > reporting SETIATHOME at 96% but not doing anything. Killing the > > service and restarting does nothing. I deleted the work unit and it > > then grabs another and works?? > > > > Should I do edit my files as you say below? > > If you didn't edited them yet, this may help to see what's happen. > if you have some trace of what's happen, please, post them. > however, if this problem is really related to how setiathome works > inside, I'll not be able to do something, since we don't have access > to the sources. so, in this case, a bug report would have to be sent > using the "bug report form" at > http://setiathome.ssl.berkeley.edu/help.html > > PS : the only thing I can do is to add a keyword to the startup > script to delete the current work unit and eventually another keyword > to check if the current work unit is still alive (well, I don't > really know how to do this, this I can't reproduce anything, do you > have any idea about that ?). > I have probably processed at least 5-10K wus with the current FreeBSD version of setiathome. The only time I have seen it do something like this is when the files are owned by a different user than the one running seti. It can run but not write to the state file. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html