Printable View
Is it possible to let a program itself capture a Kill Signal, write a log, then exit?
Say, a program is called myprog. you use
to kill it in linux.Code:killall myprog
Instead of exiting immediately, myprog writes a log about someone is killing it, and then it exits? Is there a such way?
Alas, Windows is indeed a rare breed of operating systems. Not many allow a programmer to do stuff after the OS categorically told it to die. There is no easy means of doing what you want as far as I know. But I bet you could probably change your kernel a little to allow this practice.
When you "killall myprog", myprog receives a signal, right? So can we capture the signal in myprog?
http://man.he.net/?topic=signal§ion=allQuote:
Signal handlers cannot be set for SIGKILL or SIGSTOP.
You cannot catch SIGKILL. If a process receives this signal, it immediately terminates.
You can catch pretty much any other signal, though. And 'killall' uses SIGTERM, not SIGKILL, by default. The standard practice is to catch SIGTERM.
As far as I know, the only option for what you want to do is to have another program trace the SIGKILLs that are sent. From the perspective of your program, by the time its received the signal it will soon die and has no way of doing anything once the signal is received.