My current project needs an agent to run whenever a user is logged in.
A LaunchAgent would be perfect for this, and in 10.5, it is.
If I can't use a LaunchAgent on 10.4, the alternative isn't so
appealing:
* I'd need to use barely-supported procedures to install a global
login item.
* There would be separate install, update, and uninstall code paths
for 10.4, 10.5+, and a 10.4 to 10.5+ migration
* The daemon would need to be able to detect a migration from 10.4 to
10.5+ and convert the global login item to a LaunchAgent on first boot
That's a little more complexity (and potential for a failure) than I
want. Has anyone found workarounds for the issues in 10.4? Can I
program my agent to handle the error conditions that lead to a failed
launch (detect non-gui sessions, for instance) and exit gracefully
before launchd rips it out?
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
