Foreground, Background, and Persistence Map

Separate shell jobs, persistent sessions, and supervised services so long-running work stops feeling like one vague category.

Visuals

Foreground, Background, and Persistence Map

Many process mistakes come from using the wrong running model. This visual helps learners decide whether shell job control, a persistent session, or a supervised service is the right fit.

Matrix Processes

Need the full topic around this model? Open Processes.

Diagram
Layer ModelBest forMain risk if misused
Foreground or simple background job Short or watched work in the same sessionThe work may die with the shell or session
Persistent session Reconnectable long-running shell workIt still is not the same as OS supervision or boot integration
Supervised service Long-lived workloads the OS should monitor and restartIt can hide the real cause if you keep restarting blindly
What to notice
  • Getting the prompt back is not the same as surviving disconnects.
  • Persistent sessions help you reconnect; services help the OS supervise and restart work.
  • The safest model is the lightest one that still matches the operational need.
Common confusion
  • Treating a background job as if it were persistent.
  • Using a service when a reconnectable session would have been enough.
  • Forgetting that disconnects and reboots test different promises.
Related learning
Processes 7 command anchors

What to do next

Best next step Learning

Open the lesson path when you want the full explanation behind this model.

Open now