First I would thank the list for all suggestions regarding the amrecover problem I was experiencing. As it turns out the problem was a permissions issue as noted in the debug file of amidxtaped. But why is still a mystery.
Initially I was getting a permission denied on the tape device. One suggestion was to add the group =, to the (x)inetd entry for amidxtaped. Although that did not actually fix the problem it did change the error message in the debug file. After that change I was getting a permission denied on the log file for that session. Which the fix was to set the proper group, in my case disk, for the logs directory. After that the amrecover session went fine. In my installation the amanda user is bin. Which bin belongs to the bin group and also disk group among others. I had set the log directory to owner root and group bin. Which worked fine for amdump and other amanda utilities. So at this point I am not sure why amrecover forced the issue of group = disk, while the other utilities cruise right along and can write to directories / files with the group = bin. I think on my next install I will go with the recommended user=amanda and then place that user in one group such as disk and then stay consistent across all the directories involved. Thanks again -- Jim Summers <[EMAIL PROTECTED]> University of Oklahoma - Computer Science
