[Doc] Using cron - reed-alert - Lightweight agentless alerting system for server
HTML git clone git://bitreich.org/reed-alert/ git://enlrupgkhuxnvlhsf6lc3fziv5h2hhfrinws65d7roiv6bfj7d652fid.onion/reed-alert/
DIR Log
DIR Files
DIR Refs
DIR Tags
DIR README
DIR LICENSE
---
DIR commit 0b600b142b7d503226b44ff7f58188df569898a9
DIR parent 9b9ba4d5082ee71bf28c9d0f361ee16ff64e6caf
HTML Author: Solene Rapenne <solene@perso.pw>
Date: Thu, 25 Jan 2018 19:35:30 +0100
[Doc] Using cron
Diffstat:
M README | 22 +++++++++++++++++++++-
1 file changed, 21 insertions(+), 1 deletion(-)
---
DIR diff --git a/README b/README
@@ -50,7 +50,27 @@ Start reed-alert
To start reed-alert
+ sbcl : **sbcl --script config_file.lisp**
-+ ecl : **ecl -shell config_file.lisp**
++ ecl : **ecl --shell config_file.lisp**
+
+Older versions of ecl requires -shell instead of --shell.
+
+
+Reed-alert start automation
+---------------------------
+
+You can use cron to start reed-alert every n minutes (or whatever time
+range you want). The frequency depend on what you check, if you only
+want to check the daily backup worked, running reed-alert once a day
+is fine but if you need to monitor a critical service then every
+minute seems more adapted.
+
+As always with cron jobs, be sure that either you call the interpreter
+using its full path or that $PATH inside the crontab contains it.
+
+A cron job every minute using ecl would looks like this :
+
+ */5 * * * * ( cd /opt/reed-alert/ && /usr/local/bin/ecl --shell server.lisp )
+
Personal Configuration File
---------------------------