Control and inspect background and stopped processes from the shell using the jobs command. 29.03.2026 | reading time: 2 min The `jobs` builtin shows which processes the current interactive shell is tracking as background or stopped jobs; it helps keep order when many tasks run at once. Background job demo Start a job in the background by running `sleep 100 &` which typically prints something like `[1] 12345`; then immediately run `jobs` and you will see an entry such as `[1]+ Running sleep 100 &`; bring it back to foreground with `fg %1` or stop it with Ctrl+Z and resume in background with `bg`. Job control nuances `jobs` is a shell builtin and reports only the jobs for that interactive shell session, so job numbers are local and not PIDs; use `jobs -l` to show PIDs or `jobs -p` for just PIDs; note that `jobs` may not work in non-interactive scripts unless job control is enabled, and commands like `disown` or `nohup` let you detach a job from the shell for long-running tasks. Complementary commands Use `bg` to restart a stopped job in the background, `fg` to bring a job to the foreground, and `kill` or `kill %1` to terminate by job number; for persistent sessions across logouts consider `screen` or `tmux`, or run services under `systemd` or via `nohup` when appropriate. Where to go next Practice by starting, stopping and manipulating several jobs until the workflow feels natural; mastering job control prevents accidental process loss and makes the shell a far more powerful workstation, and for deeper study consider exam preparation like CompTIA Linux+ or LPIC-1 with intensive courses at bitsandbytes.academy. Join Bits & Bytes Academy First class LINUX exam preparation. utilities processes scripting troubleshooting
