mirror of git://bitreich.org/reed-alert
[Doc] Using cron
This commit is contained in:
parent
9b9ba4d508
commit
0b600b142b
22
README
22
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
|
||||
---------------------------
|
||||
|
|
Loading…
Reference in New Issue