On Mon, Apr 29, 2002 at 01:16:46PM +0200, Arvid Gr�tting wrote:
>
> ... . Also, I *think* I've found
> a way to work around this while keeping amverify in my crontab:
>
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (/tmp/crontab.31807 installed on Sat Apr 27 13:21:02 2002)
> # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
> 3 23 * * 1-5 /usr/local/sbin/amdump nf-amanda
> 13 16 * * 1-5 /usr/local/sbin/amcheck -m nf-amanda
> 01 17 * * 1-5 /bin/mt -f /dev/nst1 retension
> 01 08 * * 2-6 /usr/local/sbin/amstatus nf-amanda || /usr/local/sbin/amverify
>nf-amanda 2> /dev/null > /dev/null
>
> This hasn't been tested yet, but the idea is that amstatus should
> return 0 ("true" to the shell) if the backups are still running, thus
> preventing the execution of the amverify.
An alternative:
prepare a shell script wrapper containing 2 (or more) lines like:
/usr/local/sbin/amdump nf-amanda
/usr/local/sbin/amverify nf-amanda 2> /dev/null > /dev/null
And change your crontab first line to:
3 23 * * 1-5 /usr/local/sbin/amdumpwrapper
That way, amverify will run when amdump happens to finish, be it
in 2 hrs or 20 hrs.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
