Hello! > If amverify is started before amdump has completed, amflush will > (sometimes, at least) proceed normally, and amdump will be unable to > go on.
> 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 I would recommend putting amdump and amverify command into single shell script and calling this script from crontab. This way you won't have to guess when amdump will finish. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Character density: The number of very weird people in the office.
