From owner-freebsd-ports@FreeBSD.ORG Mon Jun 14 20:16:28 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 F251F16A4CE for ; Mon, 14 Jun 2004 20:16:27 +0000 (GMT) Received: from smtp.volant.org (gate.volant.org [207.111.218.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id C32A443D48 for ; Mon, 14 Jun 2004 20:16:27 +0000 (GMT) (envelope-from patl+freebsd@volant.org) Received: from 64-144-229-193.client.dsl.net ([64.144.229.193] helo=[192.168.0.13]) by smtp.volant.org with asmtp (TLSv1:AES256-SHA:256) (Exim 4.30; FreeBSD) id 1BZxs8-000FVN-2D; Mon, 14 Jun 2004 13:16:00 -0700 Date: Mon, 14 Jun 2004 13:15:30 -0700 From: Pat Lashley To: Kent Stewart , freebsd-ports@freebsd.org Message-ID: <3584308672.1087244130@mccaffrey.phoenix.volant.org> In-Reply-To: <200406140410.32197.kstewart@owt.com> References: <200406140410.32197.kstewart@owt.com> X-Mailer: Mulberry/3.1.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Scan-Signature: 21326353a51681f4d0ab86360d0c6d97294237e6 X-Spam-User: nobody X-Spam-Score: -4.9 (----) X-Spam-Score-Int: -49 X-Spam-Report: This mail has matched the spam-filter tests listed below. See http://spamassassin.org/tag/ for details about the specific tests reported. In general, the higher the number of total points, the more likely that it actually is spam. (The 'required' number of points listed below is the arbitrary number above which the message is normally considered spam.) Content analysis details: (-4.9 points total, 5.0 required) -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 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 20:16:28 -0000 --On Monday, June 14, 2004 04:10:32 -0700 Kent Stewart wrote: > 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. I see the busy-but-not-updating state about once a week or so on all of my FreeBSD machines; but not Solaris or Mac OS X. When it happens to me, the file ownerships and permissions have not changed. I have found that I don't have to abandon a work unit in progress though. I just shut down the seti process(es); make sure they are gone; then delete the pid.sah and lock.sah files. (If the state.sah is empty, I delete it too.) Then restart using the rc script; and all is well. -Pat