Unix / Networks / Security / Resilience
A process should not depend on an interactive terminal longer than necessary.
In Unix, nohup arranges for a command to ignore SIGHUP. It does not protect against every failure.
nohup ./worker.sh > worker.log 2>&1 &The broader lesson: identify dependencies, design for failure, and verify recovery.
A communication path is valuable only when information arrives intact and can be trusted.
Monitor the channel. Verify the source. Preserve message integrity. Maintain an alternative route.
Reliability is engineered, not assumed.
Understand dependencies. Remove single points of failure. Test backups. Document recovery procedures. Observe the result.