Re: Launchd and terminal process launch - is there any difference from that process' viewpoint?
Re: Launchd and terminal process launch - is there any difference from that process' viewpoint?
- Subject: Re: Launchd and terminal process launch - is there any difference from that process' viewpoint?
- From: eveningnick eveningnick <email@hidden>
- Date: Mon, 8 Nov 2010 22:04:06 +0200
Hi Ken, thanks for the answer
> > Does the first one has some restrictions when it calls Accessibility
> > functions?
> It may, depending on the session type. Have you set LimitLoadToSessionType in your agent's launchd plist?
>
no, i haven't specified that
>
> > This Launch Agent is supposed to be started everytime, when the system
> > starts.
>
> When the system starts, or when a user logs in to a GUI session?
it is a "Session-start" agent. But: i can start this agent by writing
"launchctl load ~/Library/LaunchAgents/com.my.agent.label.plist"
"launchctl start com.my.agent.label"
in terminal, and i will get the same behavior - in MacOS 10.5 i
experience troubles. If i start it via terminal, it works great.
>What's the point of your agent running for a given user when that user is not logged in? You may be configuring your agent to be always running at the cost of full access to the Window Server and its services.
Is "session-kind" agent loaded when the user isnt logged in? Well i
didnt delve much into that, i only specify it's a "session-type" and
was glad it worked on Mac OS 10.6.
Maybe i should try some special options in plist? I only specified
there "Start On load", "Not On Demand", working directory and a path
to the binary.
_______________________________________________
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