From d10b4b23b1b6bbd17b871852ccd59fc3ea5dc0bd Mon Sep 17 00:00:00 2001 From: Juraj Bednar Date: Sat, 19 Feb 2022 00:07:16 +0100 Subject: [PATCH] examples and documentation --- README.md | 4 ++++ signal-monitoring.sh | 2 ++ 2 files changed, 6 insertions(+) diff --git a/README.md b/README.md index 8fb396e..7c597ba 100644 --- a/README.md +++ b/README.md @@ -26,6 +26,10 @@ port, but if the authentication succeeds. It only needs to be able to run echo c you can configure the shell to just print "ssh_connection_ok" on stdout. It does not need to be able to execute any other commands. +**check_script** takes a check identificator as the first parameter and the rest are +executed (warning, no sanity checking, we expect no user input coming to this). If the script +returns an error status, it failed (exit status >0) + The last **signal-cli** command just downloads all messages for this instance and drops them. Use this if this script is the only user using this server to ease up storage requirements for signal servers and make sure that it does not diff --git a/signal-monitoring.sh b/signal-monitoring.sh index 9aeee5d..ca7abfd 100755 --- a/signal-monitoring.sh +++ b/signal-monitoring.sh @@ -125,6 +125,8 @@ check_url my-third.server.com "https://my-third.server.com/index.html" "Welcome check_ssh "johnpb27" "my-ssh.server.com" 22 +check_script "alliswell" "/usr/local/bin/is-all-well" + # Leave this if you don't use signal-cli outside of this script, # otherwise comment out, see readme signal-cli -u $SIGNAL_USER receive > /dev/null 2>&1