• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Machine sleep & wake notifications in a daemon
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Machine sleep & wake notifications in a daemon


  • Subject: Re: Machine sleep & wake notifications in a daemon
  • From: Andrew Keller <email@hidden>
  • Date: Thu, 08 Jan 2015 17:54:05 -0500

On Jan 8, 2015, at 5:20 PM, Ken Thomases <email@hidden> wrote:

> On Jan 8, 2015, at 4:03 PM, Andrew Keller <email@hidden> wrote:
>
>> I would like to receive machine sleep and wake notifications in my daemon.  In my Cocoa GUI application, I was able to easily follow the sample code under Listing 1 on the page <https://developer.apple.com/library/mac/qa/qa1340/_index.html>, but when I tried the same approach in my daemon, I received no errors or warnings from Xcode or in the system console, and yet the handlers also did not fire.  After poking around for a while, I have a hunch that it may have something to do with the main event queue not being the same (or existing at all?) in a non-Cocoa GUI application.
>>
>> Is it possible to have a Cocoa-style event queue in a daemon, or is there another way to receive machine sleep and wake notifications from the OS in a daemon?
>
> Did you read further down that QA article you linked to listings 3 and 4?

Yes.  It looks very promising, but on the first try, I wasn't able to keep the run loop running (it exited immediately).  I suspect that the problem has to do with the run loop not having any input sources.  I'm currently in the middle of <https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/Multithreading/RunLoopManagement/RunLoopManagement.html>, where it's explaining how to create run loop sources.  I'm learning quite a lot here, but that also means that progress is very slow at the moment.  I figured it would hurt to ping the list to see if there was a simpler solution or perhaps documentation more specialized to my objective.

Also, I have a feeling that there may be something missing conceptually.  Suppose I do manage to keep the run loop running using a new input source.  How do the OS and the application frameworks know to route the notification there?  I suspect that some additional object registration may be needed to make the run loop handle the events, or it might be a very specific input source I don't know about yet...

Thanks,
 - Andrew Keller


_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden


  • Follow-Ups:
    • Re: Machine sleep & wake notifications in a daemon
      • From: Ken Thomases <email@hidden>
    • Re: Machine sleep & wake notifications in a daemon
      • From: Greg Parker <email@hidden>
References: 
 >Machine sleep & wake notifications in a daemon (From: Andrew Keller <email@hidden>)
 >Re: Machine sleep & wake notifications in a daemon (From: Ken Thomases <email@hidden>)

  • Prev by Date: deny file-read-data after launch
  • Next by Date: Re: Machine sleep & wake notifications in a daemon
  • Previous by thread: Re: Machine sleep & wake notifications in a daemon
  • Next by thread: Re: Machine sleep & wake notifications in a daemon
  • Index(es):
    • Date
    • Thread