Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Jun 2004 12:10:31 -0700
From:      Kent Stewart <kstewart@owt.com>
To:        freebsd-ports@freebsd.org
Cc:        'Edwin Groothuis' <edwin@mavetju.org>
Subject:   Re: SETIATHOME PORT
Message-ID:  <200406141210.31252.kstewart@owt.com>
In-Reply-To: <00b501c4520d$29b448f0$7890a8c0@dyndns.org>
References:  <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAv+hg2asc3kOTt0Qm5pDcf8KAAAAQAAAAT4Mm8fPif0ywmx6sO7WyIgEAAAAA@fsegura.com> <200406140410.32197.kstewart@owt.com> <00b501c4520d$29b448f0$7890a8c0@dyndns.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Monday 14 June 2004 05:43 am, Cyrille Lefevre wrote:
> "Kent Stewart" <kstewart@owt.com> 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



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?200406141210.31252.kstewart>