Bugzilla Bug 65638

when setiathome-3.08-r2 runs on machines with 2 processors, the
/var/lib/setiathome/thread2/setiathome.log will grows with errors to fill up
the space.

# tail setiathome.log
Each instance of SETI@home must run in a separate directory.
/var/lib/setiathome/setiwrapper: line 7: wait: pid 1 is not a child of this
shell
Couldn't get lock file.  This is probably because
another instance of SETI@home is running in this directory.
Each instance of SETI@home must run in a separate directory.
/var/lib/setiathome/setiwrapper: line 7: wait: pid 1 is not a child of this
shell
Couldn't get lock file.  This is probably because
another instance of SETI@home is running in this directory.
Each instance of SETI@home must run in a separate directory.
/var/lib/setiathome/setiwrapper: line 7: wait: pid 1 is not a child of this
shell

Reproducible: Always
Steps to Reproduce:
1. emerge setiathome
2. edit /etc/conf.d/setiathome, set SETIATHOME_THREADS="2"
3. /etc/init.d/setiathome start
Actual Results:  
/var/lib/setiathome/thread2/setiathome.log grows dramatically until all space
is
filled.

Expected Results:  
/var/lib/setiathome/thread2/setiathome.log stops growing up or grows much
slower.

I did a little hack on /etc/init.d/setiathome and
/var/lib/setiathome/setiwrapper to fix this problem. this is my workaround:

# diff /etc/init.d/setiathome.new /etc/init.d/setiathome
52c52
<               ${SETIATHOME_DIR}/setiwrapper thread${thread} ${SETIBINDIR}
${SETIATHOME_OPTIONS} >& setiathome.log &
---
>               ${SETIATHOME_DIR}/setiwrapper ${SETIBINDIR}
${SETIATHOME_OPTIONS} >& setiathome.log &


# diff /var/lib/setiathome/setiwrapper.new /var/lib/setiathome/setiwrapper
2,4c2,3
< cd $(dirname $0)/$1
< dir=${2}
< shift
---
> cd $(dirname $0)
> dir=${1}

Found the same problem yesterday, fixed it in /var/lib/setiwrapper only:

diff setiwrapper setiwrapper.new
2d1
< cd $(dirname $0)

Since /etc/init.d/setiathome already changes to the thread directories I simply removed the "cd ..." in setiwrapper. This way everything seems to work fine.

Thanks for reporting. Fix is in portage.