To make sure a job ran, simply mash up a bash script (or php/python) and run
an sql query for all jobs that started on a certain day. Then you could
compile this in a single readable e-mail. Then add an admin job which runs
the script at a specified time every day (preferably after your backups, so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is also a Nagios plugin for Bacula.
Michael Short wrote:
> To make sure a job ran, simply mash up a bash script (or php/python) and
> run an sql query for all jobs that started on a certain day. Then you
> could compile this in a single readable
Hi,
16.10.2007 20:32,, Ryan Novosielski wrote::
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> There is also a Nagios plugin for Bacula.
And to monitor if your jobs actually ran, use a "Run After Job" script
to send passive check results to Nagios. The passive check should use
freshness
Thanks to all for the advice. I hadn't even thought of the Nagios
passive check option. That sounds best for me - I'll look into it
tomorrow. I haven't done anything with passive checks and freshness
checking, but luckily I picked up the Nagios book - something good for
bedtime reading...
As to th
Hi,
[EMAIL PROTECTED] wrote:
> Essentially, what I'm looking for (or may be writing) is a
> little script
> (Python maybe?) that will find all jobs that should have been run this
> calendar day (I guess by parsing the director config file, since it's
> not stored in the database) and then check t
