Re: OS startup done event
Re: OS startup done event
- Subject: Re: OS startup done event
- From: Michael Smith <email@hidden>
- Date: Fri, 6 Nov 2009 10:14:05 -0800
On Nov 6, 2009, at 2:50 AM, Anil Kumar K wrote: Thanks for the response. My queries on your suggestion of launch-on-demand launch daemon are below:
1. The daemon I was referring to is an always-load launch daemon (i.e., OnDemand is set to false). We want the daemon to be always alive. So, is there a way that I make OnDemand setting to true but want the daemon to be always alive?
Why do you want it always alive? 2. My understanding of OnDemand setting is that, the daemon will be triggered on demand if OnDemand is set to true. In such case, I guess I need to write the logic to trigger the daemon. Is there any simple logic that I can add so that daemon will be triggered without impacting boot times?
OnDemand services are triggered when their clients attempt to connect. launchd proxies your listening activities (socket listens, mach ports, etc.) and launches your daemon as required to handle new connections.
It sounds like a little time with the launchd documentation might give you a few options.
= Mike
-- Ars longa, vita brevis, occasio praeceps, experimentum periculosum, iudicium difficile -- Hippocrates
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden