SIGINT and others

Sighup
SIGINT terminates process interruption
Sigquit creates a core file to terminate the process and generates a Core File
Invalid Command for creating core file in sigill
Sigtrap creates core file tracking self-traps
Sigbus Core File bus creation error
Invalid SIGSEGV Core File segment creation error
An error occurred while creating the core file floating point in sigfpe.
Sigiot creates Core File Execution I/O self-traps
Sigkill terminate the process and kill the process
Sigpipe terminates a process and writes data to an unread process pipeline.
When sigalarm terminates the process Timer
Sigterm termination process software termination signal
Sigstop stop signal of non-terminal stop Process
Sigtstp stop signal from the process Terminal
Sigcont ignores the signal and continues a stopped process.
Sigurg ignores signal I/O emergency signals
Sigio can ignore the I/O on the signal Descriptor
Sigchld ignores the signal and notifies the parent process when the child process stops or exits.
Sigttou stops the process Background Process Writing Terminal
Sigttin stops the process Background process read Terminal
Sigxgpu termination process CPU timeout
The length of the sigxfsz termination process file is too long.
Sigwinch ignores changing signal window size
Sigprof termination process statistical distribution when timer is used
SIGUSR1 termination process user-defined signal 1
Sigusr2 termination process user-defined Signal 2
When sigvtalrm terminates the virtual timer of the process

1) The sighup signal is sent at the end of the user terminal connection (normal or abnormal), usually in the terminal's control
When the process ends, each job in the same session is notified.
No longer associated.
2) The SIGINT program termination (Interrupt) signal 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 -).
The core file is generated when sigquit exits. In this sense, it is similar to a program error message.
No.
4) sigill executes invalid commands. This is usually because the executable file itself has an error or an attempt to execute
Data Segment. This signal may also be generated when the stack overflows.
5) sigtrap is generated by the breakpoint instruction or other trap instruction. It is used by the 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) sigbus illegal address, including memory address alignment error. eg: access a four-character long
But its address is not a multiple of 4.
(8) sigfpe is triggered when a fatal arithmetic operation error occurs. This includes not only floating point operation errors, but also overflow.
An error occurs in all other arithmetic operations, such as 0 in the output and devisor.
9) sigkill is used to immediately end program running. 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 with 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, this signal can be blocked and
Processing. It is usually used to require the program to exit normally. Shell Command kill will generate this by default
Signal (s.
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 be blocked.
A handler that enables a program to complete a specific task when it changes from stopped to continue execution.
Job. For example, re-display the prompt
19) sigstop stop (stopped) process execution. Note the differences between it and terminate and interrupt:
This process has not ended, but is paused. This signal cannot be blocked, processed, or ignored.
20) sigtstp stops the process, but the signal can be processed and ignored.
(Usually Ctrl-z) sends this signal
21) sigttin when the background job needs to read data from the user terminal, all processes in the job will receive sigttin
Signal. Due to lack of time, these processes will stop running.
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 by getrlimit/setrlimit/
Change
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
Time.
28) it is issued when the sigwinch window size is changed.
29) The sigio file descriptor is ready for input/output operations.
30) sigpwr Power Failure

Yes
Two signals can 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, false
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.