On Fri, Sep 4, 2009 at 12:40 AM, vinit dhatrak<vinit.dhatrak@xxxxxxxxx> wrote: > > > On Fri, Sep 4, 2009 at 12:29 AM, Laurentziu Dascalu > <dascalu.laurentziu@xxxxxxxxx> wrote: >> >> 2009/9/3 Kent Tu <kachin2@xxxxxxxxx>: >> > Is this what you are looking for? >> > http://linux.die.net/man/2/signal >> > >> > >> >> No, I can't "intercept" SIGKILL with this. I still think there is some >> kind of hackish solution to this :-? How about having a parent process and then catching SIGCHLD ??? >> >> >> -- >> Laurențiu Dascălu >> >> -- >> To unsubscribe from this list: send an email with >> "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx >> Please read the FAQ at http://kernelnewbies.org/FAQ >> > No, I dont think you even get any chance to execute some user code in case > of SIGKILL. Kernel itself kills and removes that process from the system > before it returns. Correct me if I am wrong here > > -Vinit > -- Thanks - Manish -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
