Re: Prevent SIGKILL
Re: Prevent SIGKILL
- Subject: Re: Prevent SIGKILL
- From: Michael Smith <email@hidden>
- Date: Thu, 26 Mar 2009 22:39:06 -0700
On Mar 26, 2009, at 12:08 AM, Jainish Jain wrote: I want to make a Client-Server Application in which once a client Application is connected to Server, user at client side should not be able to terminate it unless permission is given by server.
This is usually a crutch for a badly designed client/server protocol, or a badly implemented server. If you find yourself wanting this behaviour in your software, it's time to stop and re-evaluate your design, because you are in trouble.
Even if you were to remove the administrative ability for a user to terminate a task they had created, there are many other ways in which such a task may be terminated, and you must be robust in the face of such an event. I have trapped all other signals but not able to find a way to prevent SIGKILL to my Application ?
Is there any way in which my Application not launched as Startup process can prevent SIGKILL
No. The system reserves the right to mark for termination any process at any time, and it grants the creator of the process that right unconditionally.
= Mike
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden