From owner-freebsd-ports@FreeBSD.ORG Mon Jun 14 19:10:39 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 179DD16A4CE for ; Mon, 14 Jun 2004 19:10:39 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD82E43D41 for ; Mon, 14 Jun 2004 19:10:38 +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 i5EJASco017612; Mon, 14 Jun 2004 12:10:29 -0700 From: Kent Stewart To: freebsd-ports@freebsd.org Date: Mon, 14 Jun 2004 12:10:31 -0700 User-Agent: KMail/1.6.2 References: <200406140410.32197.kstewart@owt.com> <00b501c4520d$29b448f0$7890a8c0@dyndns.org> In-Reply-To: <00b501c4520d$29b448f0$7890a8c0@dyndns.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406141210.31252.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 19:10:39 -0000 On Monday 14 June 2004 05:43 am, Cyrille Lefevre wrote: > "Kent Stewart" wrote: > [snip] > > > 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. > > that's interresting, I'll add a check about not writable files in the > startup script. FWIW, in my case, you didn't have to refetch but simply chown the files so that you had write priviledges, I have an alias that checks on things as root. Berkely gets hung up occassionaly and I would forget and force run my upseti script as root. I keep about 3 days of wus on hand, which is around 18 on the faster machines. At any rate, about 3 days later, when my runseti script would get around to the wu updated by root, seti would hang. I could chown the files back to my seti user and it would continue without problems. You have a valid wu. You just couldn't write to state.sah. I would whack my forehead, swear not to do it again and that would work until I forgot the next time :). Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html