Hi,
Now that I have multiple luns working in RHEL 5 for a Tandberg drive,
I decided to upgrade
AMANDA to the latest version Amanda 2.6.0p1. I had bsdudp auth
working, but I see that in order
to get the windows client to work (eventaually), I needed to use
bsdtcp. While adding
auth "bsdtcp"
to th
By running
touch /usr/local/etc/amanda/amanda-client.conf
I was able to eliminate the error on the server (which is also a client).
I may also have pre-empted a flood of emails on this list.
Perhaps an empty amanda-client.conf file is sufficient, though I
imagine amanda-client.conf is supposed t
The problem is resolved--it was a case of RTGDMFM and
also changing the ownership of the /tmp/amanda directory
from amanda (the previous user) to amandabackup (apparently
needed in the windows client--though I should think it's only a name).
amcheck simply reports "connection refused" if
/tmp/ama
On Sun, Jun 8, 2008 at 8:07 PM, FL <[EMAIL PROTECTED]> wrote:
> However, now I have the amanda-client.conf error, which makes a cameo
> appearance in a few amanda threads,
> but either leaves the scene before the role it plays is revealed, or
> else I am now so enfeebled that I lack the energy
>
On Sun, Jun 8, 2008 at 11:13 PM, Dustin J. Mitchell <[EMAIL PROTECTED]> wrote:
> This is a result of an error-messaging bug in the 2.6.0. Basically,
> config error messages go to stderr, which xinetd routes to the server.
> The bug has been fixed in trunk, but on double-checking, it hasn't
> been
