Does enabling huponexit ensure background jobs receive SIGHUP on shell exit, or does disown override it?
When migrating a small application without downtime using Bash, a common pattern is to replace the current shell with a new binary via exec while trapping SIGTERM and SIGHUP to perform cleanup and relaunch the service. The reliability of this approach hinges on how background jobs are treated when the parent shell exits. Bash's huponexit option controls whet
bash