$RodHat_/search

$ man 7 signal · diff

SIGSTOP vs SIGTSTP

How do you pause a process?

SIGSTOP always stops the process and cannot be caught. SIGTSTP is the terminal-style stop, usually sent by Ctrl-Z; an application may catch it to restore terminal state before stopping.

FieldSIGSTOPSIGTSTP
Linux number1920
FreeBSD number1718
Default actionStop the processStop the process
Catch, block or ignoreNoYes

SIGSTOP

SIGSTOP is the unconditional stop. It is useful when a process must be frozen for inspection, but it gives the process no chance to tidy its terminal or other state first.

SIGTSTP

SIGTSTP can be caught, blocked or ignored. A full-screen terminal program can restore the terminal, stop itself, then redraw after SIGCONT. That is why Ctrl-Z can leave a usable prompt.

Rod's field note

Both leave the process in place rather than exiting it. SIGCONT resumes a stopped process. Timers, sockets and other processes do not stop just because this process did.

What to check

If Ctrl-Z appears to do nothing, inspect the foreground process group and whether the program handles or ignores SIGTSTP. Use the process state to confirm it actually stopped.

Sources and scope

Default actions and Linux numbers follow signal(7). FreeBSD numbers follow the FreeBSD signal(3) manual. Numbers shown are Linux x86/arm64 and FreeBSD; other Linux architectures may differ. Installed handlers can change observed behavior except for signals that cannot be caught.

← More signal comparisons