[launchd-dev] Yosemite not starting a system launch agent

[James Bucanek]

Damien,

Thanks for the suggestion, and apologies for the tardy reply; I just got 
buried under twenty other to-do items that were higher on the list.

I tried removing the LimitLoadToSessionType entry from my agent's plist, 
but it doesn't make any difference. When trying to install it as a 
system-wide agent, the process still doesn't start.

My reading of LimitLoadToSessionType would lead me to believe that it's 
applicable to my service, which *is* an agent. It runs as a regular 
user, and the docs would indicate that this property is just a hint to 
the load balancer on how to constrain its use of CPU/memory/IO. It 
doesn't make sense that it would keep the process from starting in the 
first place.

Anyway, I'm replying to Axel's message with a complete description of 
what I'm trying to accomplish and exactly what's not working.

James

> Damien Sorresso <mailto:dsorresso at apple.com>
> June 25, 2015 at 8:53 AM
> James,
>
> Your plist probably has the LimitLoadToSessionType key set to 
> Background, which will prevent it from loading outside of a user's 
> background session. So when you do a regular `launchctl load` from a 
> Terminal window (for example), you're targeting the Aqua session, and 
> launchd says no. Similarly, if you try and load it into the system 
> session (either by running launchctl(1) under sudo(1) or by using the 
> bootstrap subcommand with a "system" target), launchd will also say no.
>
> If you remove the LimitLoadToSession type key, you'll be able to load 
> the job wherever you'd like.
> -damien
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/launchd-dev/attachments/20150722/5b9d4f77/attachment.html>