Atlas · fluency
Processes and signals
Every running program is a process. Signals are how you ask one to stop, or make it stop.
In plain words
Each program you start, from a shell to a coding agent, runs as a process. When one hangs, you send it a signal.
How it works
POSIX defines a live process as an address space, one or more threads running in it, and the system resources they need. SIGTERM is the termination signal, a polite request a program can catch to clean up. SIGKILL cannot be caught or ignored. In a terminal, ps lists processes, kill 1234 sends SIGTERM to process 1234, and kill -9 1234 sends SIGKILL.
Going deeper
Try SIGTERM first. SIGKILL gives the program no chance to save its work, which matters when an agent is halfway through writing files.
Sources
- POSIX.1-2024 Base Definitions: Live Process The Open Group / IEEE
An address space with one or more threads executing within that address space, and the required system resources for those threads.
Many of the system resources defined by POSIX.1-2024 are shared among all of the threads within a process.
- POSIX.1-2024: signal.h The Open Group / IEEE
Kill (cannot be caught or ignored).
Termination signal.
Quotes were checked against the live pages on 2026-11-12.