Job Control: Suspend One, Background Another

A deploy is starting and two long-running jobs need different treatment. /usr/local/bin/render.sh hogs the box: PAUSE it — suspend it, don't kill it — so it can resume exactly where it left off afterwards. /usr/local/bin/indexer.sh must keep running, but out of your way: put it in the BACKGROUND so your prompt is free.

Start each one yourself, then use job control on it. The details are in /root/brief.txt. Grading reads each process's state from the kernel (what ps -o stat shows), not your keystrokes, so any route to the right state passes.

The classic mistake is Ctrl+C where you meant Ctrl+Z: one ends the process, the other freezes it.