On Dec 9, 2013, at 3:17 PM, Jim Elliott <sjameselli...@me.com> wrote: > I have a program that solves problems that are very computationally intense. > I divide up the work and create an NSOperation for each segment. Then I put > the operations in NSOperationQueue, and start the queue. Expecting the job > to take three or four hours, I go to dinner. > > When I return, and look at my progress screen, I find that processing has > stopped sometime about an hour into the job. My mouse events restart the > job, and it later completes, about four hours later than estimated. > > Apparently, after a give time interval without user intervention, MAC OS just > goes to sleep until some user input is detected. I mean not just screen > saver, but processing shutdown. > > Any ideas as to how I keep my megajob running in my absence?
Programmatically: https://developer.apple.com/library/mac/qa/qa1340/_index.html From the command line: man caffeinate -- Greg Parker gpar...@apple.com Runtime Wrangler _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
