Ticket 13133

Summary: How do I manage configuration files to avoid errors when configuration files cannot be found
Product: Slurm Reporter: zhuwq <zhuwqvip>
Component: OtherAssignee: Jacob Jenson <jacob>
Status: RESOLVED INVALID QA Contact:
Severity: 6 - No support contract    
Priority: ---    
Version: 20.11.8   
Hardware: Linux   
OS: Linux   
Site: -Other- Alineos Sites: ---
Atos/Eviden Sites: --- Confidential Site: ---
Coreweave sites: --- Cray Sites: ---
DS9 clusters: --- HPCnow Sites: ---
HPE Sites: --- IBM Sites: ---
NOAA SIte: --- OCF Sites: ---
Recursion Pharma Sites: --- SFW Sites: ---
SNIC sites: --- Linux Distro: ---
Machine Name: CLE Version:
Version Fixed: Target Release: ---
DevPrio: --- Emory-Cloud Sites: ---

Description zhuwq 2022-01-06 05:59:58 MST 
When a command needs to read the configuration file when the cluster is replacing the configuration file, an error message is displayed indicating that the configuration file does not exist. How can I avoid this situation?