>I have broken my previously working configuration... Well, that was a pretty silly thing to do! :-)
>So, why would amcheck be saying: WARNING: tapedev is /dev/null ? > >I see the man page says the amcheck uses /dev/null as the default ... There are a couple of interactions going on here. ./configure has a parameter, --with-tape-device, that sets the default tape device to be used. It's intended purpose is for amrecover, however it bleeds over into the man page and the default if tapedev is not set in amanda.conf. Next, amcheck is *only* looking at the amanda.conf tapedev value when it issues that warning. That's probably a mistake in the code when a changer is involved since the changer can return the actual device name. For your particular setup, the quick solution would be to add something like: tapedev "/changer-returns-actual-value" to amanda.conf. That should shut amcheck up. You could also rerun your ./configure (after removing config.cache) with a value along these lines for --with-tape-device, but that's a lot more work (although it would "fix" the man page). >*** A TAPE ERROR OCCURRED: [new tape not found in rack]. This error, however, has nothing to do with /dev/null (I don't think). It's saying amdump was expecting to get a new tape but it could not find one. In other words, the number of "reuse" entries in your tapelist file is less than your tapecycle value. Once you work around the tapedev silliness above, amcheck should report the same thing. Why the number of tapes is "wrong" is left as an exercise for the reader :-). >J John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
