Differences between current version and predecessor to the previous major change of SIGKILL.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 3 Last edited on Wednesday, January 28, 2009 9:34:55 am by AristotlePagaltzis
Older page: version 2 Last edited on Thursday, August 16, 2007 3:02:05 pm by BenStaz Revert
@@ -1,13 +1,9 @@
 !!!Signal: KILL 
-This signal causes your program to terminate. This signal cannot be caught or ignored. This is always signal #9. To terminate a process IMMEDIATELY, send it a signal 9. Note the process will not have a chance to clean up
+This signal causes a process to terminate immediately . It cannot be caught or ignored. This is always signal #9 on all systems
-!!kill -9 is a BAD Idea  
- The command ''kill -9 (or -KILL)'' should only be used as a very last resort!  
-The KILL signal does not allow a process to run any cleanup code, which means using ''kill -9'' may leave child processes of a parent orphaned , temporary files open , shared memory segments active , and sockets busy. This leaves the system in a messy state , and could lead to unanticipated and hard to debug problems. 
+__Do not use this signal lightly.__ The process will not have any chance to clean up. It may leave behind orphaned child processes, temporary files, allocated locks, active shared memory segments, busy sockets , and any number of other resource state inconsistencies. This can lead to surprising and hard to debug problems in the subsequent operation of the system
-* ZombieProcess'''' es in the "Z" state cannot be killed, they are dead already and are waiting on their parents to reap them  
+* ZombieProcess~ es in the "Z" state cannot be killed: they are dead already, and are merely waiting for their parents to collect their exit code.  
 * Processes that are blocked in the "D" state will not die until they recover from their D status.