On Saturday 29 June 2002 14:53, twopinkblobs@t-online.de wrote:

Just for those who might still be interested, I turned my setiathome client off and the accessing also stopped.

I set up a user specifically for running seti. The user has a starting script for the seti@home client in his ~/bin directory. It looks like this: #!/bin/sh cd ~/setifolder1; ./setiathome -nice 19 >> /dev/null 2>&1 & cd ~/setifolder2; ./setiathome -nice 19 >> /dev/null 2>&1 & I run two processes at the same time, since the system is a dual PIII, and the seti client cannot multi-thread by itself. As you can see I redirect any output from the seti client to the big bit bin. This does not hinder the seti client in doing its job properly and writing to the work files when it's necessary. It prevents the constant access to harddrives, however. The script can be run manually or started from cron. Try it out. Best regards, David List