Nohup on Margrop Blog

Your Background Process Keeps Dying After Shell Exit? Stop Blaming nohup — Understand setsid and Unix Process Lifecycle

Mon, 01 Jun 2026 07:00:00 +0800

The short version

You launched a background service. You used nohup. You added &. You redirected output. Everything looked fine. But when you closed the terminal, disconnected SSH, or—more insidiously—when an automation tool finished executing its script, the process silently vanished. You checked ps—nothing. You checked the port—nothing. No error in the logs. If this has happened to you, you’re not alone.

The root cause isn’t SIGHUP—at least, not entirely. The real issue is process group and session membership. nohup merely tells the process to ignore the SIGHUP signal, but the process still belongs to the same session and process group as the parent shell. When the shell exits and sends SIGHUP to the entire process group, nohup helps—but only if the signal delivery chain stops there. If the controlling terminal is destroyed, if stdin/stdout pipes break, or if the parent’s process group is collectively reaped, the process can still die. The proper fix is setsid: it creates a brand-new session, detaches from the controlling terminal, and places the process in its own process group—so SIGHUP from the parent shell never reaches it in the first place.

This post is based on a real debugging session of the CLIProxyAPI service. The service was started with nohup but kept disappearing every time an automation script finished. The management panel kept showing “connection failed.” The culprit turned out to be a subtle Unix process lifecycle issue. This class of problem is common in cloud dev machines, CI runners, SSH jump hosts, and containerized workflows, but it’s often misdiagnosed because the underlying process model is poorly understood.

All private details have been removed. No real internal addresses, tokens, or paths appear in this article.

Installing Frp Client on CentOS with SSH Access

Sat, 23 Jan 2021 17:22:58 +0800

Download and Extract Frp

Latest Frp download address: https://github.com/fatedier/frp/releases/

mkdir ~/frp
cd ~/frp
wget https://github.com/fatedier/frp/releases/download/v0.35.0/frp_0.35.0_linux_amd64.tar.gz
tar -xvzf frp_0.35.0_linux_amd64.tar.gz

Ubuntu installs Frp server, non-client

Sat, 23 Jan 2021 13:43:20 +0800

Download and extract FRP Latest FRP release: https://github.com/fatedier/frp/releases/ cd ~ mkdir frp cd frp wget https://github.com/fatedier/frp/releases/download/v0.35.0/frp_0.35.0_linux_amd64.tar.gz tar -xvzf frp_0.35.0_linux_amd64.tar.gz cd frp_0.35.0_linux_amd64 Configure FRP Remove the default client configuration file Create the server configuration file cd ~/frp/frp_0.35.0_linux_amd64/ rm frpc rm frpc.ini rm frpc_full.ini ls -a sudo su rm frps.ini cat>/etc/frps.ini<<EOF [common] # FRP server bind port bind_port = 1000 # Set the HTTP access port to 1001 vhost_http_port = 1001 # Set the domain name (make sure it is reachable) subdomain_host = frp.