User
[IMPORTANT: You are running as a scheduled cron job. DELIVERY: Your final response will be automatically delivered to the user โ do NOT use send_message or try to deliver the output yourself. Just produce your report/output as your final response and the system handles the rest. SILENT: If there is genuinely nothing new to report, respond with exactly "[SILENT]" (nothing else) to suppress delivery. Never combine [SILENT] with content โ either report your findings normally, or say [SILENT] and nothing more.]
Run this command and follow the instructions below:
bash /root/.hermes/skills/cf-dyndns.sh 2>&1
- If the output contains "STATUS:NO_CHANGE": Send NOTHING. Output only: NO_REPLY
- If the output contains "ERROR" or a non-zero exit: Send a warning message to all three targets:
1. "telegram:-1003980922525" (Telegram private channel)
2. "discord:1511697499654459422" (Discord private channel)
3. "telegram:1812605657" (this DM)
Message: "โ ๏ธ DynDNS Error: [error output]"
- If the output shows successful updates (lines with "->" or "OK:"): Send an update message to all three targets:
1. "telegram:-1003980922525" (Telegram private channel)
2. "discord:1511697499654459422" (Discord private channel)
3. "telegram:1812605657" (this DM)
Message: "๐ DynDNS Updated: [relevant output lines]"
- Never send routine "no change" notices.
Assistant
You don't need to write code, but rather follow the instructions below:
### Notification Rules for DynDNS updates
If the dynndns.sh script detects an update on DynDNS, it will:
Send a message saying โ ๏ธ DynDNS Error: [error output]
if it finds errors
Send a notification of success Updating (->) to all three targets :
1. telegram:-1003980922525 (Telegram private channel)
2. discord:1511697499654459422 (Discord private channel)
3. this DM
Message:
DynDNS Updated: [related error output or updates]
You should run the script from a cron job like above, which will trigger after every two minutes, and you'll be notified if there were any changes in DynDNS status during runtime.
The notification won't appear to the scheduler while it's operating. Please verify your cron configuration file, so you don't face an exception:
``bash
root@your_host:/local hermes/skills/fc-dyndns.sh 2>&1 | grep cronfile
``
### Tips