Complete the header template across Partnership, Kernel, Deployment and Plugin
Finishes the pass: every script now documents its safeguards, and the deliberate absences in the sourced libraries are recorded so they are not "corrected" later.
This commit is contained in:
@@ -36,6 +36,29 @@
|
||||
# All three failed → notify, manual intervention needed → exit 1.
|
||||
#
|
||||
# ==============================================================================================
|
||||
# DESIGN PRINCIPLES
|
||||
# ==============================================================================================
|
||||
#
|
||||
# Lightest Fix First
|
||||
# Escalation runs cheapest-to-heaviest, and stops the moment the WebGUI answers. Most
|
||||
# hangs clear with a php-fpm restart; going straight to the heavy remedy would take the
|
||||
# whole management interface down for a fault a service reload would have fixed.
|
||||
#
|
||||
# The WebGUI Is Not the Server
|
||||
# An unresponsive WebGUI does not mean an unhealthy machine. Docker, the array and every
|
||||
# share keep working while emhttp is wedged, so nothing here reboots or touches storage —
|
||||
# the remedy stays scoped to the web stack.
|
||||
#
|
||||
# Verify After Every Step
|
||||
# Responsiveness is re-tested between escalation steps rather than assuming a restart
|
||||
# worked. Without that the script would walk the full ladder every time, restarting
|
||||
# services that were already fixed one step earlier.
|
||||
#
|
||||
# Silent When Healthy
|
||||
# Runs every cycle via system_watchdog.sh and prints nothing on a working WebGUI. A
|
||||
# per-minute "all good" line would bury the one cycle that mattered.
|
||||
#
|
||||
# ==============================================================================================
|
||||
# OPERATIONAL SAFEGUARDS
|
||||
# ==============================================================================================
|
||||
#
|
||||
|
||||
Reference in New Issue
Block a user