View the supported signal list in Linux

View supported signal lists in Linux :~ $ Kill-l1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL5) SIGTRAP 6) SIGABRT 7) SIGBUS 8) SIGFPE9) SIGKILL 10) SIGUSR1 11) SIGSEGV 12) SIGUSR213) SIGPIPE 14) SIGALRM 15) SIGTERM 17) SIGCHLD18) SIGCONT 19) SIGSTOP 20) SIGTSTP 21) SIGTTIN22) SIGTTOU 23) SIGURG 24) SIGXCPU 25) signature) SIGVTALRM 27) SIGPROF 28) SIGWINCH 29) SIGIO30) SIGPWR 31) SIGSYS 34) SIGRTMIN 35) SIGRTMIN + 1
36) SIGRTMIN + 2 37) SIGRTMIN + 3 38) SIGRTMIN + 4 39) SIGRTMIN + 540) SIGRTMIN + 6 41) SIGRTMIN + 7 42) SIGRTMIN + 8 43) SIGRTMIN + 944) SIGRTMIN + 10 45) SIGRTMIN + 11 46) SIGRTMIN + 12 47) SIGRTMIN + 1348) SIGRTMIN + 14 49) SIGRTMIN + 15 50) SIGRTMAX-14 51) SIGRTMAX-1352 53) SIGRTMAX-12 54) SIGRTMAX-10 55) SIGRTMAX-956 SIGRTMAX-8 57) SIGRTMAX-7 SIGRTMAX-6 59) SIGRTMAX-560 61) SIGRTMAX-4 62) SI GRTMAX-2 63) SIGRTMAX-164) SIGRTMAX www.2cto.com signal Brief Description: SIGHUP termination process terminal line hanging up SIGINT terminate process interrupt process SIGQUIT establish CORE file terminate process, and generate the core file SIGILL create CORE File Illegal command www.2cto.com SIGTRAP build CORE file tracking self-trapped SIGBUS build CORE file Bus Error SIGSEGV build CORE file segment illegal error SIGFPE build CORE file floating point exception SIGIOT build CORE file execute I/O self-trapped SIGKILL terminate process killing process SIGPIPE terminate Process Writing data to a pipeline without reading process SIGALARM terminate process timer then SIGTERM terminate process software terminate signal SIGSTOP Stop process non-Terminal stop Signal SIGTSTP stop process terminal stop signal SIGCONT ignore Signal Continue to execute a stopped process SIGURG ignore signal I/O emergency signal SIGIO ignore signal descriptor can be I/OSIGCHLD ignore signal when the child process stops or exits, notify the parent process SIGTTOU stop process Background process write terminal SIGTTIN stop process Background process read terminal SIGXGPU terminate process CPU time-out SIGXFSZ terminate process file Length Too Long SIGWINCH ignore signal window size change SIGPROF terminate process statistical distribution chart when timer is used SIGUSR1 terminate Process user-Defined signal 1SIGUSR2 termination process user-defined Signal 2 SIGVTALRM termination process virtual timer at the time of www.2cto.com signal details: 1) The SIGHUP signal is sent at the end of the user terminal connection (normal or abnormal). Generally, when the control process of the terminal ends, it notifies all jobs in the same session, they are no longer associated with the control terminal. 2) SIGINT program termination (interrupt) Signal, which is sent when you type the INTR character (usually Ctrl-C. 3) SIGQUIT is similar to SIGINT, but it is controlled by the QUIT character (usually Ctrl. A process generates a core file when it exits after receiving SIGQUIT. In this sense, it is similar to a program error signal. 4) The SIGILL command is invalid. it is usually because an error occurs in the executable file or an attempt to execute a data segment. this signal may also be generated when the stack overflows. 5) SIGTRAP is generated by breakpoint commands or other trap commands. used by debugger. 6) when the SIGABRT program finds an error and calls abort. 6) SIGIOT is generated by iot instructions on the PDP-11, and is the same as SIGABRT on other machines. 7) An error occurred while alignment of the SIGBUS illegal address, including memory address alignment. eg: access an integer with four characters in length, but its address is not a multiple of 4. www.2cto.com 8) SIGFPE is issued when a fatal arithmetic operation error occurs. not only include floating point operation errors, but also This includes overflow, Division 0, and other arithmetic errors. 9) SIGKILL is used to immediately end the running of the program. this signal cannot be blocked, processed, or ignored. 10) SIGUSR1 is reserved for users 11) SIGSEGV tries to access the memory not allocated to itself, or try to write data to the memory address that has no write permission. 12) SIGUSR2 is reserved for users. 13) SIGPIPE Broken pipe 14) The SIGALRM clock timing signal calculates the actual time or clock time. the alarm function uses this signal. 15) The SIGTERM program terminate signal. Unlike SIGKILL, the signal can be blocked and processed. it is usually used to require the program to exit normally. shell Command kill generates this signal by default. www.2cto.com 17) when the SIGCHLD sub-process ends, the parent process will receive this signal. 18) SIGCONT allows a stopped process to continue execution. this signal cannot Blocked. You can use a handler to make the program complete specific work when it changes from the stopped status to continue execution. For example, re-display the prompt. 19) SIGSTOP stops (stopped) The execution of the process. note the difference between it and terminate and interrupt: the process has not ended, but the execution is paused. this signal cannot be blocked, processed, or ignored. 20) SIGTSTP stops the process, but the signal can be processed and ignored. this signal is sent when you type the SUSP character (usually Ctrl-Z. 21) SIGTTIN when the background job needs to read data from the user terminal, all processes in the job will receive the SIGTTIN signal. the process stops running due to lack of time. 22) SIGTTOU is similar to SIGTTIN, but it is received when the write terminal (or modify the terminal mode. 23) SIGURG has "urgent" data or out-of-band data generated when it reaches the socket. 24) The SIGXCPU exceeds the CPU time limit. this limit can be read/changed by getrlimit/setrlimit 25) SIGXFSZ exceeds the file size resource limit. 26) SIGVTALRM virtual clock signal. similar to SIGALRM, the CPU time occupied by the process is calculated. 27) SIGPROF is similar to SIGALRM/SIGVTALRM, but includes the CPU time used by the process and the system call time. 28) it is issued when the SIGWINCH window size is changed. 29) The SIGIO file descriptor is ready and can be started. Input/Output operation. www.2cto.com 30) SIGPWR Power failure has two signals to stop the process: SIGTERM and SIGKILL. SIGTERM is relatively friendly, and processes can capture this signal and close the program as needed. Before closing the program, you can end the opened record file and complete ongoing tasks. In some cases, if a process is running and cannot be interrupted, the process can ignore this SIGTERM signal. Processes cannot ignore SIGKILL signals. This is a signal "I don't care what you are doing, stop immediately. If you send a SIGKILL signal to the process, Linux stops the process.