I've used Amanda for four years or so now in two different contexts,
but I've only recently made the following observation:
If amverify is started before amdump has completed, amflush will
(sometimes, at least) proceed normally, and amdump will be unable to
go on. Amdump does not, however, seem
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)
> #
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
> 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
This solution
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)
> #
I've used Amanda for four years or so now in two different contexts,
but I've only recently made the following observation:
If amverify is started before amdump has completed, amflush will
(sometimes, at least) proceed normally, and amdump will be unable to
go on. Amdump does not, however, seem
