Ok I got it, I was making it way too hard again. Re-read the manual's triple checked the configs, folders, permissions and rebooted the server and everything is working now. Figured out there was two things incorrect in my setup and they were. FreeBSD has to have operator:operator not amanda:disk for permissions over the amanda client to allow it to properly read so I redid the port with the default permissions and just set the server and it worked right off the bat after doing the second part. Found a write up showing me there are some directories and files that are not created using the port as well that I had to make and set permissions on. So for those that have a problem with it here is the link for FreeBSD 4.9 port install write up and how to fix it.
Http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2003-November/018025.h tml Jason > From: Matthias Andree <[EMAIL PROTECTED]> > Date: Tue, 28 Sep 2004 21:27:08 +0200 > To: Jason Miller <[EMAIL PROTECTED]> > Cc: Matthias Andree <[EMAIL PROTECTED]>, > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > Subject: Re: Amanda Client > > Jason Miller <[EMAIL PROTECTED]> writes: > >> The below is exactly what is in my xinetd.conf and I have added amanda to it >> to my hosts.allow and to insure everything is good to go I went as far as >> rebooting the machine. > > Running amcheck with -c on the server might be another, more lightweight > way to check if the client is fine. > > BTW, I just remembered that amanda also needs its own access control > file configured, so you'd also do (this is sh syntax not csh if in doubt): > > echo "bigstore.example.org amanda" >~operator/.amandahosts > > replace bigstore.example.org by the server's hostname. Depending on the > DNS setup, you may need to do this as well: > > echo "bigstore amanda" >>~operator/.amandahosts > > -- > Matthias Andree > > Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)
