Maybe it is too late to suggest this, but FWIW...
I'm running the linux client on my one linux box at home. It is slower than molasses -- just one WU a day -- but then the box is a PII 333 Mhz (w/ 66 Mhz bus). But the box is used for little else than a SSH tunnel to the rest of my home lan, so I might as well put the wasted cycles to use doing something, even if only one WU a day.
I haven't tried the win client with wine. It doesn't appeal to me. I don't mix my peas and mashed potatoes. And I don't mix linux and windows.
😀 (Well, not entirely true; I'm a big fan of samba, and don't hestitate to use linux for file and print services on windows networks.)
IAC, I found the following link to be a pretty straight-forward explanation of how to install and run the linux seti client:
http://www.parkut.com/setifarm/linux.htm
I
haven't been able to get a chrontab to work, for some strange reason. I use one on a linux box at school to automate a backup, so I have
some experience with chrontab.
But after logging on locally as root and starting the seti client, and then logging back off, my remote SSH login shows that the client has been running 9 days, 12 hours, 47 minutes, and 22 seconds nonstop.
I don't normally put seti on servers, just workstations. But this is an obvious exception, since the server does nothing except validate an occasional SSH login and tunnel connections to other windows clients on my home LAN.
IAC, if you want to give the linux client a try, the instructions in the above link are pretty straightforward. If you have any further questions (about installing or running the linux client, not running windows client under wine), just ask.
-Baz