Thanks for your response. I think perhaps my question wasn't clear.
I'm trying to work around the documented limitation in launchd (on
Tiger) that prevents it from being used to launch a process at user
login. The limitation, as I understand it, is that there's no way to
prevent launchd from launching the process even if the user logs in
via a non-GUI method like ssh.
So, I guess what I'm asking is if, *once I have been launched as a
Login Item*, I can leverage launchd to simply re-launch me properly if
I should crash. Or, does a subsequent launch-on-crash suffer the same
basic problem that prevents launching me at login in the first place?
If using launchd won't cut it, is there an alternative approach for
not just launching me at login, but also re-launching me if I crash?
Obviously, I don't anticipate crashing, but the project requirements
I've been handed specify automatic re-launching of this background
helper app, and I'd prefer to find a way to satisfy the requirements
rather than argue to have the requirement removed.
Thanks again,
--Mike
PS: "KeepAlive" is the 10.5 option. In 10.4, it was "OnDemand", which
is now deprecated.
So, what I'm wondering is: is there any way to use launchd to give me
the automatic restart that I need, on Tiger? One thing I had thought
of doing is to have myself launched as a Login Item, but once
launched, to *add myself* to launchd's list so that if I should
crash,
I'll get re-launched.
Hmm. Wasn't there something like KeepAlive, now deprecated?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
