Linux process Signal

Linux Process signal SIGHUP terminate process terminal line hang up SIGINT terminate process interrupt process Sigquit build core file terminate process and generate core file Sigill build core file non- Sigtrap Set up core file tracking self-trapping Sigbus establish core file bus error SIGSEGV establish core file segment illegal error SIGFPE build core file floating point exception Sigi OT build core File Execution I/o self-trapping sigkill terminate process kill process sigpipe terminate process to a pipe without a read process write data sigalarm terminate process timer to sigterm terminate process software termination signal sigstop Stop process non-terminal to stop signal SIGTSTP stop process terminal to stop signal sigcont ignore signal continue to perform a stopped process Sigurg ignore signal I/o emergency signal sigio ignoring signal descriptors can be performed on I/OSIGCHLD Ignore signal when a child process stops or exits notifies the parent process Sigttou stop process background process write terminal Sigttin stop process background process read Terminal SIGXGPU terminate process CPU time-out SIGXF     SZ termination process file length too long sigwinch ignore signal window size changes sigprof terminate process statistics distribution graph with timer to time SIGUSR1 terminate process user-defined signal 1SIGUSR2 terminate process User-defined signal 2SIGVTALRM terminates the process virtual timer to the time1SIGHUP This signal is issued at the end of the user terminal connection (normal or abnormal), usually at the end of the control process of the terminal to notify the same session of the various jobs, when they are no longer associated with the control terminal.2) SIGINT program termination (interrupt) signal, type intr characters in the user (typically Ctrl-C) when issued3Sigquit and SIGINT are similar, but by the quit character (usually Ctrl-) to control. The process generates a core file when it receives a sigquit exit, similar to a program error signal in this sense.4) Sigill executed an illegal instruction. This is usually due to an error in the executable file itself or an attempt to execute a data segment. This signal can also be generated when a stack overflows.5SIGTRAP is generated by a breakpoint instruction or other trap instruction. Used by debugger.6SIGABRT The program itself discovers the error and calls abort.6) Sigiot in pdp-11 is generated by the IoT directive, and SIGABRT on other machines.7) Sigbus illegal address, including memory address alignment (alignment) error. Eg: accesses an integer with a length of four words, but its address is not a multiple of 4.8The SIGFPE is emitted when a fatal arithmetic operation error occurs. This includes not only floating-point arithmetic errors, but also all other arithmetic errors such as overflow and divisor 0.9SIGKILL is used to immediately end the run of the program. This signal cannot be blocked, processed and ignored.Ten) SIGUSR1 left to the user to use OneSIGSEGV tries to access memory that is not assigned to itself, or attempts to write data to a memory address that does not have write permissions. A) SIGUSR2 left to the user to use -) Sigpipe Broken pipe -) SIGALRM clock timing signal to calculate the actual time or clock time. The alarm function uses this signal. theThe SIGTERM program end (terminate) signal, unlike Sigkill, is that the signal can be blocked and processed. Usually used to ask the program to exit normally. The shell command kill generates this signal by default. -The parent process receives this signal when the SIGCHLD child process ends. -Sigcont let a Stop (stopped) process continue execution. This signal cannot be blocked. You can use a handler to get the program to do certain work when the stopped state changes to continue. For example, to re-display the prompt +) SIGSTOP the execution of the Stop (stopped) process. Notice the difference between it and terminate and interrupt: The process is not over yet, just pause execution. This signal cannot be blocked, processed or ignored. -The SIGTSTP stops the process from running, but the signal can be processed and ignored. When a user types Susp characters (usually ctrl-Z) Send this signal +Sigttin When a background job reads data from a user terminal, all processes in that job receive a sigttin signal. By default, these processes stop executing. ASigttou is similar to Sigttin, but is received when writing a terminal (or modifying terminal mode). at) Sigurg has"Emergency"Data or out-of-band data is generated when the socket is reached. -SIGXCPU exceeds the CPU time resource limit. This limit can be read by Getrlimit/setrlimit/Change -) Sigxfsz exceeds the file size resource limit. -) sigvtalrm the virtual clock signal. is similar to SIGALRM, but calculates the CPU time that is consumed by the process. -) Sigprof similar to sigalrm/SIGVTALRM, but includes the CPU time used by the process and the time of the system call. -sigwinch The window size is changed. in) The SIGIO file descriptor is ready to begin input/output operation. -the SIGPWR Power failure has two signals to stop the process: Sigterm and Sigkill. Sigterm is friendly and the process captures the signal and shuts down the program according to your needs. Before you close the program, you can end the open record file and complete the task you are doing. In some cases, if the process is working and cannot be interrupted, the process can ignore the sigterm signal. For Sigkill signals, the process cannot be ignored. This is a "I don't care what you are doing, stop immediately" signal. If you send a sigkill signal to the process, Linux will stop the process there http://blog.sina.com.cn/s/blog_4b226b92010119k1.html

Linux process Signal