Re: Prevent SIGKILL
Re: Prevent SIGKILL
- Subject: Re: Prevent SIGKILL
- From: Terry Lambert <email@hidden>
- Date: Thu, 26 Mar 2009 00:46:15 -0700
On Mar 26, 2009, at 12:08 AM, Jainish Jain wrote:
Hi ,
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.
Client side User should not be able to terminate Client Application
by kill -9 <pid> or Force Quit from Activity monitor
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
Any help would be really great
Personally, I'd just yank the network cable if some application did
that to me. And if that didn't work, there's the power cord. Thne
there's mounting the disk in another machine, and deleting every trace
of the client software that did that in the first place.
Fortunately, the issue will never actually come up:
<http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html
>
"The system shall not allow a process to catch the signals SIGKILL
and SIGSTOP."
because you simply can't intercept certain signals.
-- Terry
_______________________________________________
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