A Couple launchd user agent questions
A Couple launchd user agent questions
- Subject: A Couple launchd user agent questions
- From: Steve Sisak <email@hidden>
- Date: Wed, 20 Feb 2008 14:41:28 -0500
I have an application that really wants to be a launchd agent, but is
currently a global login item for compatibility with Tiger, where
user agents don't work correctly.
Since I'm in the process of doing a release and have the installer
open, I'm considering making it an agent on Leopard for future
compatibility.
This leads to a couple questions (not fully answered by "man launchd.plist"):
1) Is there a way to set up the plist so that it will load under
Leopard and newer, but not under Tiger? (If not, I can have my
installer postflight script delete the plist file under Tiger and it
will work fine as a global login item if the user upgrades the OS)
2) I'm assuming that should call "launchctl unload my-agent.plist"
during my installer preflight and will shut down all copies in all
users and then call "launchctl load my-agent.plist" in my postfight
to bring it back up for all users. Are there any other issues I need
to worry about -- like if a running application has a connection to
one of my agents mach ports?
3) I'm familiar with setting up a launch daemon for launch on demand
with unix domain sockets -- for the agent, I need to do the same with
a few mach ports. Is there a decent example of a plist for mach
ports? Also, can I include the security session ID in the port name?
Thanks,
-Steve
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden