Lists

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: Guy Meyer <email@hidden>
Date: Wed, 29 Nov 2006 07:14:33 +0200


Thanks for answers.

Just to clarify the question, the two process communicate nicely and the child process terminates when it should nicely.

The problem is that sometime a user can force quit the parent process for whatever reason and only in this case the child process keeps running and consumes computing resource, a situation I am trying to avoid.

Guy
_______________________________________________

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>)
  >Re: Slightly OT: SIGKILL (force quit) and child process termination (From: email@hidden)




Prev by Date:
Re: Checking if a file is Locked

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