No, I didn't terminated them.There was delay in manager communication with daemon. It seems daemon was hung for more than 30 seconds - all apps exited with no heartbeat message. I see that message in SETI's stderr (MW tasks already gone of course).
...STD ~13500s now and still increasing....
....If so - and this is the difficult bit - how do we get it to manage all that tricksy CPU / GPU / GPU pretending to be a part of a CPU / multithreaded CPU (active at AQUA) stuff, add GSTD resource-share scheduling, and still make it driveable by both a teenager and their granny?
Quote from: Richard Haselgrove on 10 Jul 2009, 05:16:28 pm....If so - and this is the difficult bit - how do we get it to manage all that tricksy CPU / GPU / GPU pretending to be a part of a CPU / multithreaded CPU (active at AQUA) stuff, add GSTD resource-share scheduling, and still make it driveable by both a teenager and their granny? I'm working on the premise that we can fudge the input figures, such that it stabilises and does what it's told. It seems to be somewhat similar in intelligence to my goldfish that only ever floated upside down, and a little below my dog 'Bozley', which is relatively intelligent compared to the goldfish (He responds to the word 'Biscuits' favourably, anyway.).
But does he respond to the word 'biscuits' in all 182,898 regional accents and dialects spoken by active SETI users - including those from cultures where the concept of 'biscuit' is entirely missing?
My STD is 6.26 with my 850-SETI/150-MW settings.