Graceful shutdown in Go Fiber without dropping in-flight requests
Stop a Fiber server without dropping active requests. Use signal handling and app.Shutdown with a context timeout to drain in‑flight work, then exit cleanly.
Loading…
ReadMeFeed / Community knowledge
#signal-handling
Real questions. Useful conversations. Find the people who know your stack.
fiberManaging Signal Dispositions Across Fork and Exec
Learn how signal dispositions are inherited during fork() and reset during exec(), and how to use SIG_IGN to preserve process behavior across binary replacements.
unixzsh and OS Kernel: Signal Propagation Order for Concurrent Background Jobs
Zsh manages background processes through a built-in job control system, utilizing signal traps to handle process termination and interrupts across concurrent tasks. While the shell facilitates the execution of multiple background jobs via the & operator, the actual scheduling and signal delivery are handled by the underlying Unix kernel. A technical unce
PM2 graceful reload vs Node.js SIGTERM handling across versions
Integration boundary PM2's zero-downtime reload mechanism relies on sending SIGUSR2 to the master process, which then forwards SIGTERM to workers for graceful shutdown. The application must implement a SIGTERM handler that finishes in-flight requests before exiting. This contract sits at the boundary between PM2's process orchestration and the Node.js runtim
pm2
nodejsDoes 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
bashOrphaned compiler processes persist after Ctrl+C in parallel Spack builds
When a user interrupts a Spack build that uses the -j parallel job flag with SIGINT (Ctrl+C), the expectation is that Spack forwards the signal to all child build processes and removes the associated staging directory. In practice, observations show that compiler or make processes may remain active after the interrupt, and the $SPACK_STAGE directory is somet