Dear Amanda maintainers... As already noted, my ssh problems are all solved, BUT...
I still have no backups at all, since upgrading to 2.5.1. The server creates the directory on the holdingdisk (that directory has a timestamp as its name), and then Amanda complains that it can't write anything on it. Then it deletes that (still empty) directory. While it lasts, that empty directory is owned by root. Its permissions are drwx------. If it were owned by amanda (my Amanda user is "amanda"), I suspect I wouldn't be having these problems. Or if the permissions included group write/search permissions. The same kind of problem applies to my tapelist file. Amanda changes its permissions, and then it can't read it during the next run. which prevents any tapers from doing any useful work. Does anyone have any ideas about why this is happening? Is my amanda.conf file THAT weird? I'm attaching it herewith. -- Steve Steven R. Newcomb, Consultant Coolheads Consulting Co-editor, Topic Maps International Standard (ISO/IEC 13250) Co-editor, draft Topic Maps -- Reference Model (ISO/IEC 13250-5) [EMAIL PROTECTED] http://www.coolheads.com direct: +1 540 951 9773 main: +1 540 951 9774 fax: +1 540 951 9775 208 Highview Drive Blacksburg, Virginia 24060 USA (Confidential to all US government personnel to whom this private letter is not addressed and who are reading it in the absence of a specific search warrant: You are violating the law and you are co-conspiring to subvert the Constitution that you are sworn to defend. You can either refuse to commit this crime, or you can expect to suffer criminal sanctions in the future, when the current administration of the United States of America has been replaced by one that respects the rule of law. I do not envy you for having to make this difficult choice, but I urge you to make it wisely.)
amanda.conf
Description: Binary data