On Sunday, September 19, 2010 07:58:13 pm Dustin J. Mitchell did opine: > On Sun, Sep 19, 2010 at 5:40 PM, Gene Heskett <[email protected]> wrote: > > Your guess is as good as mine, there simply isn't anything to indicate > > the failure, or a hint of a reason in the logs I've grepped. All I > > know at this point is that I have to back up to about svn3341 just to > > get amflush to work. The current 3419? taps the drive, once for a > > read that may be the tape header file, and once about 2 seconds later > > for a very quick write which might be the status file, then exits > > silently in another second or so even when amflush is run with the -f > > option. > > > > I think it might help if taper was made a lot more chatty. Is there a > > debug level option I could pass to it? > > Sure - add 'debug taper 9' to amanda.conf. But the taper doesn't have > anything to chat about - the driver never asks it to do anything after > starting it up. > > Dustin
But that kills amcheck, when amcheck is svn3341. How new do I have to be to have that work? [r...@coyote amanda]# su - amanda -c "vim /usr/local/etc/amanda/Daily/amanda.conf" [r...@coyote amanda]# su - amanda -c "amcheck Daily" "/usr/local/etc/amanda/Daily/amanda.conf", line 116: configuration keyword expected amcheck: errors processing config file -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) I have not yet begun to byte!
