The seti stuff appears to be working again. I think they just
had some bad data batches. I'm running it on 6 cpus at idprio.
Hmm.. seems to effect responsiveness some, sounds like something
in the scheduler that we should be able to fix :-)
-Matt
To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-hackers" in the body of the message
