Hi,

I've noticed two odd phenomena in the current SETI@home classic client
running on x86 (32-bit) Linux (both 2.4.x and 2.6.x kernels, via the SuSE
9.1 distribution):


1) The SETI@home client tends to "stall" occasionally--maybe once each
day--and must be manually stopped and restarted to get it going again.

2) The extrapolation of the remaining time is non-linear, indicating that
progress near the beginning and end of the work unit proceed much faster
(leading to a low time-remaining estimate) and slower in the middle
(leading to a high time-remaining estimate).


Has anybody else noticed these phenomema? Does anyone know why they
happen? In the case of (1), is there a way to prevent this problem?

If it might matter, I run SETI@home via Ksetiwatch.

Thanks.

Randall Schulz