On Tue, Jun 1, 2010 at 12:26 PM, Michael Ash <michael....@gmail.com> 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. --Kyle Sluder _______________________________________________ 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
