Re: What exactly happens when I perform a force quit?
Re: What exactly happens when I perform a force quit?
- Subject: Re: What exactly happens when I perform a force quit?
- From: Dan Shoop <email@hidden>
- Date: Thu, 13 Jan 2011 04:45:29 -0500
On Jan 13, 2011, at 12:48 AM, Chris Suter wrote:
> Hi Alex,
>
> On Thu, Jan 13, 2011 at 7:15 AM, Alexander Golec
> <email@hidden> wrote:
>
>> I've recently finished an intensive intro course to OS's, and I'm looking at my computer in a new light. I have a few questions I'd appreciate it if someone would take the time to answer.
>>
>> First, what exactly happens when I perform a force quit on something? Secondly, how would I go about figuring this out on my own?
>
> It's probably implemented by sending SIGKILL to the program. Type "man
> signal" in terminal. Not sure how you would have known to look there.
Obviously it's a signal being sent, what's not clear is which signals are sent and if you "Force Quit" more than once if those signals are escalated.
Normally a HUP, TERM, and KILL is the escalation a sysadmin might issue.
`man kill` might be useful too for those unfamiliar with kill'ing processes. It's all fairly standard unix/posix stuff.
As for investigating this, sc_usage and dtrace (a very excellent tool, thankful it made it into OSX from Solaris) are very useful in viewing process calls and events. Instruments is a dtrace GUI (though limited.)
-d
------------------------------------------------------------------------
Dan Shoop
email@hidden
GoogleVoice: 1-646-402-5293
aim: iWiring
twitter: @colonelmode
_______________________________________________
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