From 5e63e3da6b8ed70ca0fe4c4527f3fea605f7d1db Mon Sep 17 00:00:00 2001 From: ETWen Date: Thu, 20 Aug 2026 11:03:44 +0800 Subject: [PATCH] fix(bmc): Give bmc_monitor_ddr its own log so the two can run together Both scripts defaulted to LOG_NAME="bmc_poll.log", and PID_FILE is derived from it, so the monitor and the DDR stress shared one log and one pid file -- while the whole point of the split is to run them at the same time. The failure was quiet rather than loud: is_running greps the pid's cmdline for its own SCRIPT_NAME, so the second script did not recognise the first as running and started anyway. prepare_log_on_start then truncated the log the first one was writing (START_LOG_MODE=new), both raced on the pid file, and a later stop could only reap whichever wrote it last, orphaning the other. bmc_monitor_ddr.sh now uses bmc_ddr.log, which also moves its pid file to bmc_ddr.pid. Both remain covered by the *.log ignore rule. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_014RetWKFZFG1ZHcitQAyhwM --- src/Script_ABC_Blanton/Blanton_Script/bmc_monitor_ddr.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/Script_ABC_Blanton/Blanton_Script/bmc_monitor_ddr.sh b/src/Script_ABC_Blanton/Blanton_Script/bmc_monitor_ddr.sh index ef8d106..9c51f94 100644 --- a/src/Script_ABC_Blanton/Blanton_Script/bmc_monitor_ddr.sh +++ b/src/Script_ABC_Blanton/Blanton_Script/bmc_monitor_ddr.sh @@ -69,7 +69,7 @@ LOG_STDERR=0 # Logging LOG_DIR="" # empty =