1 views collected around this technical thread.
This article explains how to achieve graceful shutdown for Java applications by using Linux kill signals, JVM SignalHandler registration, Runtime.addShutdownHook, and Spring Boot's actuator shutdown endpoint, providing code examples and configuration details for safe resource cleanup.
Starting with Kubernetes v1.33, the Alpha feature ContainerStopSignals introduces a Pod‑level lifecycle.stopSignal field that lets platform teams specify which Unix signal (e.g., SIGINT, SIGUSR1) should be sent to containers on termination, overcoming the previous reliance on image‑defined STOPSIGNAL and improving graceful shutdown control across Linux and Windows workloads.
This article explains how the Linux SIGPIPE signal is generated during broken TCP connections, why the default kernel handling can terminate Go services that call Rust code via cgo, and provides practical code examples to ignore SIGPIPE and avoid silent process exits.
This article explains how the SIGPIPE signal is generated in Linux, why it can cause Go‑Rust services to crash without a core dump, and how to prevent it by configuring the signal handler to ignore SIGPIPE.
This article explains how to implement graceful shutdown for Go programs, covering signal handling with os/signal, closing HTTP servers without interrupting active connections, managing goroutine lifecycles, and providing complete example code for both the standard net/http package and the Gin framework.
This article introduces the Go‑based G.S library for graceful application shutdown, analyzes common container‑related pitfalls, explains its lightweight architecture with TerminateSignal and WaitingUnit modules, provides installation steps, a complete usage example, and detailed code explanations to help developers implement reliable signal handling.
This comprehensive guide explains how to containerize Java applications by choosing appropriate base images, deciding between JDK and JRE, selecting a JVM, handling graceful shutdown signals, configuring memory limits, managing DNS caching, and optionally compiling to native binaries with GraalVM.
This article explains how Android native developers can capture and recover from controllable SIGSEGV crashes by registering signal handlers and using sigsetjmp/siglongjmp to emulate a try‑catch mechanism, complete with sample JNI code and practical considerations.
This article provides a detailed Bash scripting tutorial covering conditional statements (if/elif/else, case), various loop constructs (for, while, until, select), control commands (break, continue, shift), signal handling with trap, and several practical example scripts such as a multiplication table, colored triangle, and chessboard pattern.
This article examines classic smooth upgrade strategies for HTTP services, highlights their limitations, and provides a detailed analysis of Facebook’s graceful restart library for Go, including code examples, signal handling, process inheritance, and the mechanisms for zero‑downtime deployments.
This article explains how to capture and report both Java and native crashes on Android using the Eagle Eye monitoring system, detailing the use of Thread.UncaughtExceptionHandler, Linux signal mechanisms, sigaction registration, alternative stacks, and native stack parsing with libbacktrace to improve app stability.
xCrash is an open‑source Android SDK that reliably captures both Java and native crashes across Android 4.0‑9.0 and multiple CPU architectures by using async‑signal‑safe handlers, a dedicated dumper process, and pre‑allocated resources to generate tombstone‑style dump files without root, offering richer diagnostics than BreakPad and extensible future features.
This tutorial explains how to implement hot‑reloading of Go configuration files by manually sending Unix signals, covering the creation of a signal‑listening goroutine, use of the signal.Notify API, selective handling with select, and a complete example that loads JSON config on SIGUSR1.
To implement a graceful hot restart for a Go HTTP service, the program listens for SIGHUP, forks a child process that inherits the listening socket via an extra file descriptor, the parent stops accepting new connections and shuts down while the child begins serving, ensuring uninterrupted client requests.
To prevent loss of asynchronous tasks and data corruption during application restarts, this article explains how to safely shut down the JVM using shutdown hooks, custom signal handling, and proper hook implementation, while highlighting risks of forced termination and best‑practice considerations.