Hi All,
Man page of waitpid give expansion with example on how to send SIGSTOP, SIGCONT and SIGKILL/SIGTERM to a running process. If we don't implement waitpid system call we will not be able to observer the states of process when we issue a signal to running process.
-Anand Moon
From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
To: Darshan Ghumare <darshan.ghumare@xxxxxxxxx>
Cc: kernelnewbies <Kernelnewbies@xxxxxxxxxxxxxxxxx>
Sent: Thursday, January 19, 2012 8:56 PM
Subject: Re: SIGKILL
To: Darshan Ghumare <darshan.ghumare@xxxxxxxxx>
Cc: kernelnewbies <Kernelnewbies@xxxxxxxxxxxxxxxxx>
Sent: Thursday, January 19, 2012 8:56 PM
Subject: Re: SIGKILL
Hi again :)
On Thu, Jan 19, 2012 at 16:03, Darshan Ghumare
<darshan.ghumare@xxxxxxxxx> wrote:
> What if, there is one process which is in middle of a syscall which has
> infinite loop in it received SIGKILL & there are no other processes in the
> system?
infinite loop such as "for(;;)" ? well as long as it doesn't disable
or masked out the timer interrupt, sooner or later timer interrupt
will kick in. It then followed by the usual tick handler. Inside it,
IIRC, will provoke the current running process to check queued signal
and handle it.
if the process then killed and no other process is running (are you
sure? not even kernel threads?), then kernel will enter idle state.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
