Ksetiwatch crashing

[Greg Harper]

Got ksetiwatch(latest update) on Mandrake 9.1 and 9.0. Two different machines. It crashes on closing or at least gives the error on 9.1 but doesn't on 9.0. Any idea why?
Also what's the best set-up to get the most units completed using linux and win 2000. I've got three units running on the home network.:t

[RampageIII]

You'll probably have better luck asking at the forum

http://sourceforge.net/forum/forum.php?forum_id=3004

There are a few linux users here but I don't know which versions they use.

[Logan[TeamX]]

I've never run KSETIWatch, sorry :(

I always have one Win-box running SETIQueue that handles all proxy requests, even from Linux clients. My testing days with Knoppix are suspended till cancer research is done, but I ran the i686-3.03 and 3.08 clients through SETIQueue flawlessly.

I know it's not the exact answer you were looking for, but it's an alternative! :t

Logan

[Greg Harper]

Thanks guys,
The Linux versions seem to run a little faster than windows but not a significant amount. Setiwatch only crashes when I close it in 9.1 but it doesn't lose any stats so I guess it's a bug in shutdown. The same program is flawless all the way in 9.0 Mandrake so it then points at the 9.1 version having a flaw.
Either way it still performs it's purpose I was just curious. Not being much into programming in Linux.
Question two was what I really wanted to know which was what settings or setup maximized the processing speed of either program (windows and linux).:t

[Logan[TeamX]]

When my "Win-tel" boxes are crunching for SETI, they're all running the 3.03 CLI and SETI Driver. One machine (normally the one holding the SETIQueue server) runs SETIWatch, to keep track of things.

If I run in Linux... I run the i686 3.03 client, no other tools for Linux. I just point them straight away to the SETIQueue server as a proxy server, and it caches a few days' worth of WUs for each Linux client. Normally I don't point the Win2K boxes at the SETIQueue simply because SETI Driver holds its own cache of WUs.

Some people are worried about the buffer-overflow exploit for the 3.03 client. One of the guys on the S@H message boards has written a simple program that checks the workunits to ensure that no line within exceeds 64 characters. It's called "qchk", and I host it off my website, along with a lot of other neat files for SETI and whatnot: http://www.one87.net/~teamx

The SETITeam (http://www.setiteam.com) site also hosts a lot of the files that I've mentioned.

[Greg Harper]

Thanks Logan---you've been most helpful.
I'm coming on slowly but steady. Won't have any more boxes to add though I'll have to make do with what I have.:D