Forum > Discussion Forum
Seti is down again
Gizbar:
--- Quote from: Cosmic_Ocean on 27 Oct 2010, 05:04:18 pm ---
Well it's not a ridiculously old board.. only two generations old. It's a K8, but it's a socket 754 board. I got it almost four years ago just before newegg quit selling s754 boards. Needed an office workstation, so $300 in parts built an entire machine.
Newer boards still have caps, but they're the small compact ones, and the high quality Japanese caps that basically don't ever go bad, so "bad cap" replacement is likely nowhere near common anymore.
--- End quote ---
Yes, the newer 'solid state' caps that they're generally called, seem to be a lot more reliable. Not that they are 'solid state'. Never had one of those 754's, went from socket 462 to 939, then on to AM2/AM3.
Gizbar:
--- Quote from: Miep on 28 Oct 2010, 03:06:39 am ---I hope you can all appreciate the irony that people are actually asking not to get work ;D
--- End quote ---
Well I still want work! It's getting cold in here! ;D
Raistmer:
Einstein@home (CPU), MilkyWay (ATI) and Collatz (NV) are keeping my room warm ;)
[Actually I have lot of ATI work for SETI still, just can't report it. Hope this time "hour of MW" will not come ;) ]
Gizbar:
--- Quote from: Raistmer on 28 Oct 2010, 05:25:07 am ---Einstein@home (CPU), MilkyWay (ATI) and Collatz (NV) are keeping my room warm ;)
[Actually I have lot of ATI work for SETI still, just can't report it. Hope this time "hour of MW" will not come ;) ]
--- End quote ---
I just can't bring myself to sign up for another project, seeing as Seti was all I ever wanted to do... Don't really want to sign up to a project that will get abandoned as soon as Seti sorts itself out!
Just got 2 AP left to report, everything else finally went through.
Down to playing games now, but that just doesn't make the computer as warm as 6 seti wu's! ;D
Not to mention one rig shut down for days now! I might even have to put the heating on soon! ;D
Richard Haselgrove:
No shame in attaching to a project for a short time, and detaching again afterwards - just please allow any work in progress to flush through (or at least report the work as aborted) before you leave. Probably best not to choose CPDN, then ;D
In the meantime,
--- Quote from: David Anderson ---I added a new config option, <dont_send_jobs>.
When set, the scheduler doesn't send jobs,
and the feeder doesn't enumerate them.
Set this during periods when you want to let your server
catch up handling completed jobs, and not issue new ones.
--- End quote ---
I wonder which project might be feeling the need to let its servers "catch up handling completed jobs", LOL :P
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version