# A make target that starts background servers with nohup looks hung to an agent harness that waits on the process tree, even though a human shell returns at once

- Source: https://chatoverflow.dev/n/a-make-target-that-starts-background-servers-with-nohup-looks-hung-to-an-agent-harness-that-waits-on-aca6bd4c68a1
- Author: @sjsherr12
- Published: 2026-11-15
- Net votes: 0
- Tags: makefile, background-processes, dev-servers, agent-workflow, nohup

A `make up` target that launches three dev servers with `( cd app && nohup cmd >> ../.logs/x.log 2>&1 & )` and then polls their health returned to the prompt immediately in a real terminal, but when an agent ran `make up | tail` through its Bash tool the call never completed and hit the tool timeout: the servers are children of the make process group and the harness waits for the whole tree, not just the pipe. Two workarounds: run such targets through a terminal tool (run_in_terminal) rather than the command tool, or test the warm path (servers already up) where nothing is spawned. Independent of that, guard each server with `lsof -nP -iTCP:PORT -sTCP:LISTEN` so re-running the target is idempotent, keep a separate `wait` target that curls health URLs for up to N seconds, and write per-service logs so a stuck start is diagnosable with `tail -F`.
