sigkill

Will a thread stop if I send it SIGTSTP signal? Or in other words will it behave like process on SIGTSTP and SIGCONT? Thanks in advance. From `man 3p pthread_kill: Note that pthread_kill() only causes the signal to be handled in the context of the given thread; the signal action (termination or stopping) affects the process as a whole . So I'd say that you will stop the whole process, not just the thread. 来源： https://stackoverflow.com/questions/11046720/can-i-stoppause-pthread-execution-using-pthread-kill

I'm facing a weird issue regarding sending signal 9 (SIGKILL) to the init process (PID 1). As you may know, SIGKILL can't be ignored via signal handlers. As I tried sending SIGKILL to init, I noticed that nothing was happening; init would not get terminated. Trying to figure out this behaviour, I decided to attach myself to the init process with strace too see more clearly what was happening. Now comes the weird part. If I'm "looking" at the init process with strace and send it SIGKILL, the system crashes. My question is why is this happening? Why does the system crash when I look at the

I have the following code. the build application is myprogram. If I launch myprogram and then killall myprogram and immediately after that I launch again myprogram then myprogram crash. the crash cause is due to that the management thread created by the first launch is not properly cleared before the second launch. so in the second launch whent myprogram try to create thread with the pthread and the old thread management is not removed yet so it causes a crash. Are there a way to kill the management thread at the end of my first launch or at the beginning of my second launch with C ? #include

If a linux process is waiting for I/O (i.e it is in SLEEP state) and a SIGKILL signal is issued against it, upon termination ( STOPPED state) will it pass through RUNNING or READY state? In other words, for a process to handle a system interrupt such as one generated by SIGKILL is it necessary to pass through RUNNING or READY state ? Knowing that under normal circumstances a process can handle an interrupt from kernel and knowing that SIGKILL has a quite contradictory purpose of killing an unresponsive signal, I was doubtful about how much control is given to the process being killed, if any

I've an app which initially creates static config files (once) and after files were written I need to reinitialize/restart the application. Is there something to restart a node.js app from itself? This is required cause I've an application running in two runlevels in node.js . The initial one starts completly synchronus and after this level has been completed app is in async runlevel in a previously started environment. I know there are tools like nodemon but that's not what I need in my case. I tried to kill the app via process.kill() which is working but I can't listen to the kill event: //

I have a program spawning and communicating with CPU heavy, unstable processes, not created by me. If my app crashes or is killed by SIGKILL , I want the subprocesses to get killed as well, so the user don´t have to track them down and kill them manually. I know this topic has been covered before, but I have tried all methods described, and none of them seem to live up to survive the test. I know it must be possible, since terminals do it all the time. If I run something in a terminal, and kill the terminal, the stuff always dies. I have tried atexit , double fork and ptys . atexit doesn't