Axel, I do not believe there have been any fixes in that area. The teardown path is pretty straightforward, and the code path is such that the SIGKILL timer won't ever be armed without first calling kill(2) with SIGTERM. -damien
> On 17 Apr, 2016, at 09:23, Axel Luttgens <axel.luttg...@skynet.be> wrote: > > >> Le 8 avr. 2016 à 17:38, Damien Sorresso a écrit : >> >> Axel, >> >> Your understanding is correct. My guess is that your daemon is, for whatever >> reason, not processing the SIGTERM launchd sends at shutdown. You might want >> to give you signal handling code a second look. If you're not already I'd >> recommend using dispatch(3) to handle the signal. >> >> -damien >> >>> On Mar 12, 2016, at 02:22, Axel Luttgens wrote: >>> >>> Hello, >>> >>> From launchd.plist(5): >>> >>> […] >>> >>> This is with Mac OS X 10.11.3. >>> >>> Am I misunderstanding the role of that ExitTimeOut key? > > Hello Damien, > > Thank you for your kind follow-up. > > I thus tried again today with the same daemon/plist, and… it works as > expected. > > The only difference is that I installed Mac OS X 10.11.4 on March 16th. > > Could it be that some launchd bug has been corrected with 10.11.4? > > Axel > > _______________________________________________ > launchd-dev mailing list > launchd-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/launchd-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ launchd-dev mailing list launchd-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/launchd-dev
