diff --git a/docs/en/docs/sysmonitor/sysmonitor-usage.md b/docs/en/docs/sysmonitor/sysmonitor-usage.md index a159c221cd42e442d20868c24ad6966212b67f04..7900e0b2f3f63107567238ae24cf1d7af927f532 100644 --- a/docs/en/docs/sysmonitor/sysmonitor-usage.md +++ b/docs/en/docs/sysmonitor/sysmonitor-usage.md @@ -170,7 +170,7 @@ The configuration items are as follows: - If the configured key service does not exist in the current system, the monitoring does not take effect and the corresponding information is printed in the log. If a fatal error occurs in other configuration items, the default configuration is used and no error is reported. - The permission on the configuration file is 600. You are advised to set the monitoring item to the **service** type of systemd (for example, **MONITOR_COMMAND=systemctl status irqbalance**). If a process is monitored, ensure that the **NAME** field is an absolute path. - The restart, reload, and stop of sysmonitor do not affect the monitored processes or services. -- If **USE_CMD_ALARM** is set to **on**, you must ensure the validiy of **ALARM_COMMAND** and **ALARM_RECOVER_COMMAND**. If **ALARM_COMMAND** or **ALARM_RECOVER_COMMAND** is empty or not configured, no alarm is reported. +- If **USE_CMD_ALARM** is set to **on**, you must ensure the validity of **ALARM_COMMAND** and **ALARM_RECOVER_COMMAND**. If **ALARM_COMMAND** or **ALARM_RECOVER_COMMAND** is empty or not configured, no alarm is reported. - The security of user-defined commands, such as the monitoring, recovery, stopping, alarm reporting, and alarm recovery commands, is ensured by users. Commands are executed by the user **root**. You are advised to set the script command permission to be used only by the user **root** to prevent privilege escalation for common users. - If the length of the monitoring command cannot be greater than 200 characters. Otherwise, the process monitoring fails to be added. - When the recovery command is set to a systemd service restart command (for example, **RECOVER_COMMAND=systemctl restart irqbalance**), check whether the recovery command conflicts with the open source systemd service recovery mechanism. Otherwise, the behavior of key processes may be affected after exceptions occur.