This question already has an answer here:
- How signals work internally? 3 answers
This is how I think Linux signals work:
Each process have a default signal handler for each signal, some signals's default signal handler terminates the process, while other signals's default signal handler simply ignores the signal, etc.
The following table shows all the actions that a default signal handler can take (this table is from this documentation):
Term Default action is to terminate the process.
Ign Default action is to ignore the signal.
Core Default action is to terminate the process and dump core (see core(5)).
Stop Default action is to stop the process.
Cont Default action is to continue the process if it is currently stopped.
Am I correct so far?
Now my question is: Are there some signals that you cannot override their default signal handler?