SIGHUP is a POST request

Nginx needs to reload its config. The classic sequence: SSH in, ps aux | grep nginx, squint at PIDs, kill -HUP the right one.

The Hoody sequence: POST /api/v1/system/process/signal with {"name": "nginx", "signal": "SIGHUP"}. By name or by PID, any Unix signal. The reload happens; you never opened a shell.

Which means the whole signal vocabulary is now addressable from anywhere HTTP reaches: a deploy script sends SIGTERM to the old worker, your phone kills the runaway process from a parking lot, an agent SIGHUPs a service after rewriting its config: no shell session, no PID hunting, no SSH.

SIGHUP is a POST request.