Re: Solution to quit-problem
Re: Solution to quit-problem
- Subject: Re: Solution to quit-problem
- From: BevInTX <email@hidden>
- Date: Mon, 06 May 2013 09:14:34 -0500
Jörgen,
I don't know the definitive answer; however, since you don't use kill
with a specific signal, it is sending TERM (SIGTERM) to your app, as is
shown in the following excerpt from the kill man page:
-s signal_name
A symbolic signal name specifying the signal to be sent
instead of the default TERM.
SIGTERM can be caught by a process, which allows it to perform a clean
shutdown, including releasing of memory, file closures, etc. A process
can also ignore this signal.
So, it looks to me like it should work okay for you, as long as your
process does the normal thing of shutting down cleanly after receiving it.
Bev in TX
On 5/6/13 4:18 AM, Jörgen Stahle wrote:
... portion snipped ...
*do shell script*"kill " &*my*gAppID
/instead/ of
*continue**quit*
This never fails, so it /seems/ to bee a good solution. My question here
is if there is any unobvious consequences with the method – such as that
RAM or virtual memory will not be emptied the right way. Does anybody know?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden