Re: Simulating app termination
Re: Simulating app termination
- Subject: Re: Simulating app termination
- From: Michael Ash <email@hidden>
- Date: Wed, 2 Jun 2010 11:35:26 -0400
On Tue, Jun 1, 2010 at 3:34 PM, Kyle Sluder <email@hidden> wrote:
> On Tue, Jun 1, 2010 at 12:26 PM, Michael Ash <email@hidden> wrote:
>> If your goal is to simulate shutdown/restart termination, this won't
>> work; the system does not send signals to your app to kill it during
>> those situations.
>
> TN2083 is ambiguous about this. Here's the relevant section:
>
>> This program is killed because the window server keeps track of the processes that are using its services. When you log out, the system (actually loginwindow) tries to quit these. For each GUI process, it sends a 'quit' Apple event to the process. If any GUI process refuses to quit, loginwindow halts the logout and displays a message to the user.
>>
>> The situation for non-GUI processes is slightly different: loginwindow first tries to quit the process using a 'quit' Apple event; if that fails it terminates the program by sending it a SIGKILL signal. There is no way to catch or ignore this signal.
>>
>> The upshot of this is that, if your process connects to the window server, it will not survive a normal logout."
>
> So it's clear that non-GUI apps get a quit event and then a SIGKILL,
> but it doesn't say anything about GUI apps that don't acknowledge the
> quit event.
It's not 100% clear whether it applies, but "refuses to quit" could
certainly be taken as also applying to apps which don't handle the
event at all.
Mike
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden