Forums | MacLife

Yes, at some point, the "is anything running" test (to use the technical term ) was changed to ignore either nice'd or background-only processes.  Since I wanted my computer to continue crunching workunits, I didn't look further into the specifics, but just set the computer sleep preference to "never".  I do set a separate display sleep, so I save some power when the computer's just crunching.

Is the reason sah stops after completing a unit because you don't have a persistent Internet connection or because you're telling it to stop?  Well, either way, if you leave your computer on all night, it shouldn't use that much power after it's done crunching (just sitting idle with the screen blanked), so that would be my recommendation.

As for 10.2.8, I can't judge, but I doubt the PM changes would help with this.  Given people's problems (including my own), I wouldn't install it.

Alright, I think I've worked around my problem here.

After setting the Sleep timer to 1 minute to test a solution, I let SETI run directly in the Terminal (as opposed to using SetiDockling) with the -verbose command (as in ./setiathome -verbose).

The display shut off after one minute, but the computer did not sleep.

It did not work, however, without the -verbose command.

So now it should not go to sleep after half an hour if it is not finished the work unit. Hopefully, it will go to sleep if it did finish it.

I just thought I'd let everyone know.