• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Slightly OT: SIGKILL (force quit) and child process termination
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Slightly OT: SIGKILL (force quit) and child process termination


  • Subject: Re: Slightly OT: SIGKILL (force quit) and child process termination
  • From: Cameron Hayne <email@hidden>
  • Date: Tue, 28 Nov 2006 13:13:44 -0500

On 28-Nov-06, at 11:18 AM, Guy Meyer wrote:

Looking at Terminal.app and it is child processes (login, bash), when you SIGKILL one of them, for example bash, the child process that had been launched through it is also being killed. If you SIGKILL the terminal all its child processes are also killed.

Obviously, as SIGKILL is none catchable the SIGKILL is also being sent by the Kernel to the child processes.

I think the signal is sent to all processes in the same "process group" - see 'man setpgid'


--
Cameron Hayne
email@hidden


_______________________________________________

Cocoa-dev mailing list (email@hidden)

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


References: 
 >Slightly OT: SIGKILL (force quit) and child process termination (From: Guy Meyer <email@hidden>)

  • Prev by Date: Re: Invalid number in bound text field
  • Next by Date: Re: Problem drawing directly to bitmap rep using NSGraphicsContext
  • Previous by thread: Re: Slightly OT: SIGKILL (force quit) and child process termination
  • Next by thread: Re: Slightly OT: SIGKILL (force quit) and child process termination
  • Index(es):
    • Date
    • Thread