kstewart at owt.com
Mon Jun 14 11:10:42 GMT 2004
On Monday 14 June 2004 03:40 am, Cyrille Lefevre wrote:
> "Rob Craig" <rcraig at fsegura.com> wrote:
> > Hello all,
> > Had had loads of problems over the last few days. Looks like the
> > problem is related to the work unit. Same symptoms as before. TOP
> > reporting SETIATHOME at 96% but not doing anything. Killing the
> > service and restarting does nothing. I deleted the work unit and it
> > then grabs another and works??
> > Should I do edit my files as you say below?
> If you didn't edited them yet, this may help to see what's happen.
> if you have some trace of what's happen, please, post them.
> however, if this problem is really related to how setiathome works
> inside, I'll not be able to do something, since we don't have access
> to the sources. so, in this case, a bug report would have to be sent
> using the "bug report form" at
> PS : the only thing I can do is to add a keyword to the startup
> script to delete the current work unit and eventually another keyword
> to check if the current work unit is still alive (well, I don't
> really know how to do this, this I can't reproduce anything, do you
> have any idea about that ?).
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.
More information about the freebsd-ports