Re: launchd wrong behavior for nonexistent paths and crashed services
Re: launchd wrong behavior for nonexistent paths and crashed services
- Subject: Re: launchd wrong behavior for nonexistent paths and crashed services
- From: Terry Lambert <email@hidden>
- Date: Wed, 17 Sep 2008 12:19:37 -0700
On Sep 17, 2008, at 6:30 AM, Cristescu Alexandru wrote:
> Mac OS X 10.4 had a limit
> (LAUNCHD_FAILED_EXITS_THRESHOLD). What was the reason
> to remove it ?
You could as Dave or file a bug. But see above; there are legitimate
reasons for persistently retrying. Probably they outweighed the
likelihood of an actually broken plists remaining installed or
exporting a service legitimately required by some other process and
the system remaining functional.
1. If option 'KeepAlive' is more powerful than the old 'OnDemand'
from Tiger, why there isn't an (sub)option, something like
'MaxRetries', to control the number of successive failures before
launchd aborts the task?
2. Why this new comportment to retry infinitely is not documented?
I guess you missed the part where I said you could ask Dave or file a
bug.
-- Terry
_______________________________________________
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