<p>Is it possible to run SETI when BOINC fails to do anything? For example, when I ran , I got back...</p>

2004-09-27 18:34:19 [---] Starting BOINC client version 4.09 for powerpc-apple-darwin
2004-09-27 18:34:19 [SETI@home] Project prefs: no separate prefs for home; using your defaults
2004-09-27 18:34:19 [SETI@home] Host ID is 207984
2004-09-27 18:34:19 [---] General prefs: from SETI@home (last modified 2004-09-18 17:16:36)
2004-09-27 18:34:19 [---] General prefs: no separate prefs for home; using your defaults
2004-09-27 18:34:19 [SETI@home] Deferring communication with project for 1 hours, 44 minutes, and 58 seconds
2004-09-27 18:34:19 [SETI@home] Deferring communication with project for 1 hours, 44 minutes, and 58 seconds

<p>So, me being me, I'm running SETI. Is there a way to check if BOINC is idle, and if so to run SETI for one WU. Then after the WU, try again with BOINC?</p>

Are you saying that you want to run Seticlassic if Seti Boinc scheduler is not responsing? Check this post...


My name is Pascal and this message has no meaning, but still has my approval...

It is 10 oclock, do you know what your WUWUs are doing tonight...

</p>"Are you saying that you want to run Seticlassic if Seti Boinc scheduler is not responsing?"</p><p>Exactly! I'm keeping the SETI and BOINC/SETI files in two separate directories, and want to do something like this:</p>

RUN boinc
IF boinc IS IDLE THEN
     KILL boinc
     RUN seti -stop_after_xfer
ELSE
     PUT boinc IN BACKGROUND
END IF

<p>I'm sorry if this looks like newbie pseudo-code, but I want to make the idea as clear as possible.</p><p>"Check this post..."</p><p>It didn't suggest how to accomplish it. So far, SETI and BOINC/SETI have played very well together.</p>