Hello amanda-users, I�m writing to you, because -surprise- I have a problem. I set up Amanda 2.4.2 last week on our Suse Linux-box. I took all the (working) config-files from my recent installation and modified them for the new host.
I tried running amcheck and got the message "Access as amanda not allowed from root@linux" Spent 2 days looking through mail-archives, edited my .amandahosts, moved it to /root, to ~/amanda, did the chmod 0600, the chown amanda, tried this and that. Found some mail from John R. Jackson, in which he described the problem very detailed. Did all the steps, checked everything ... Finally I built the security-binary in the common-src-dir, ran it, and it ran through ok. The one thing I don�t quite understand is, that it wants to have the .amandahosts-file at /root/.amandahosts while I configured with --WITH-USER=amanda I had some earlier amanda-installation on the machine which I removed because of amrecover-problems. My questions: Is there an explanation for the failing amcheck while security runs through ? Should I remove amanda completely again and configure-compile-install from scratch to get it right ? If yes, is there some kind of checklist I can go through to be sure I removed EVERYTHING ? I posted a similar question last week and followed the instructions given by one of you (don�t have the mentioned mails with me ...). I am hoping for your help, because I would really like to get up a running backup-schedule soon. For this week I have to trust in some coworker running some tar-commands to at least have a copy of our files in case of some failure because for this week I�m on travel. Thank you, Stefan mailto:[EMAIL PROTECTED]
