From owner-freebsd-ports@FreeBSD.ORG Mon Jun 14 20:45:52 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 6761F16A4CE for ; Mon, 14 Jun 2004 20:45:52 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF81E43D1F for ; Mon, 14 Jun 2004 20:45:49 +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 i5EKiIco021157; Mon, 14 Jun 2004 13:44:19 -0700 From: Kent Stewart To: Pat Lashley Date: Mon, 14 Jun 2004 13:44:21 -0700 User-Agent: KMail/1.6.2 References: <200406140410.32197.kstewart@owt.com> <3584308672.1087244130@mccaffrey.phoenix.volant.org> In-Reply-To: <3584308672.1087244130@mccaffrey.phoenix.volant.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406141344.21841.kstewart@owt.com> cc: rcraig@fsegura.com cc: Cyrille Lefevre cc: 'Edwin Groothuis' cc: freebsd-ports@freebsd.org 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:45:52 -0000 On Monday 14 June 2004 01:15 pm, Pat Lashley wrote: > --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. > > This is interesting. I login as seti when I boot a system and run it from that users account. I also have my own run and update scripts. I never see the hang except when I have caused it. The caching scheme I use has a directory with the machine name and a number. Each wu is processed by the setiathome executable in that directory. I run it at a nice of 19 and that lets anything run that needs to. The only exception is on 5.x where it always consumes resources. If I am doing a system upgrade or a large portupgrade on 5.x, I kill the running seti process. I have thought about running the linux-686 version which out produces the FreeBSD version by 25% or more but never got around to it. It didn't run when I tried it and I wasn't going to add some of the linux capability just to run setiathome. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html