zealfire · April 8, 2018 06:33
diff --git a/Uninterruptible sleep b/Uninterruptible sleep
 Uninterruptible sleep
 An uninterruptible sleep state is a sleep state that won't handle a signal right away. It will wake only as a result of a waited-upon resource becoming available or after a time-out occurs during that wait (if specified when put to sleep). It is mostly used by device drivers waiting for disk or network IO (input/output). When the process is sleeping uninterruptibly, signals accumulated during the sleep will be noticed when the process returns from the system call or trap.

 In Unix-like systems the command 'ps -l' uses code "D" for the uninterruptible sleep state of a process.[7] Such processes cannot be killed even with SIGKILL and the only non-sophisticated way to get rid of them is to reboot the system.[
	Uninterruptible sleep
	An uninterruptible sleep state is a sleep state that won't handle a signal right away. It will wake only as a result of a waited-upon resource becoming available or after a time-out occurs during that wait (if specified when put to sleep). It is mostly used by device drivers waiting for disk or network IO (input/output). When the process is sleeping uninterruptibly, signals accumulated during the sleep will be noticed when the process returns from the system call or trap.

	In Unix-like systems the command 'ps -l' uses code "D" for the uninterruptible sleep state of a process.[7] Such processes cannot be killed even with SIGKILL and the only non-sophisticated way to get rid of them is to reboot the system.[