[FEATURE] Signal utilisation #25
Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
| Header | Header | Header | Header | Header |
|---|---|---|---|---|
| SIGHUP | (1): | Hangup detected on controlling terminal or death of controlling process. | ||
| SIGINT | (2): | Interrupt from keyboard (Ctrl+C). | ||
| SIGQUIT | (3): | Quit from keyboard (produces core dump). | ||
| SIGILL | (4): | Illegal Instruction. | ||
| SIGABRT | (6): | Abort signal from abort(3). | ||
| SIGFPE | (8): | Floating-point exception. | ||
| SIGKILL | (9): | Kill signal (cannot be caught or ignored). | ||
| SIGSEGV | (11): | Invalid memory reference. | ||
| SIGPIPE | (13): | Broken pipe: write to pipe with no readers. | ||
| SIGALRM | (14): | Timer signal from alarm(2). | ||
| SIGTERM | (15): | Termination signal (default for kill). | ||
| SIGUSR1 | (10) | User-defined signals. | ||
| SIGUSR2 | (12): | User-defined signals. |
Commandline syntax:
kill -SIGUSR1 <pid>
kill -10 <pid>Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.