kstewart at owt.com
Mon Jun 14 19:10:39 GMT 2004
On Monday 14 June 2004 05:43 am, Cyrille Lefevre wrote:
> "Kent Stewart" <kstewart at owt.com> 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.
> 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 :).
More information about the freebsd-ports