> -Original Message-
> From: Jean-Louis Martineau [mailto:martin...@zmanda.com]
> Sent: Wednesday, June 30, 2010 5:41 PM
> To: McGraw, Robert P
> Cc: 'amanda-users@amanda.org'
> Subject: Re: connection refued when switching to bsdtcp
>
>
> McGra
On Wed, Jun 30, 2010 at 4:16 PM, McGraw, Robert P wrote:
> The host hertz is both the amanda server and client.
If this is the case, then you can use auth "local" instead, and avoid
any problems with bsdtcp. That was brave of you to try to upgrade,
change auth, and change username all at once!
McGraw, Robert P wrote:
inetadm -l amanda/udp
SCOPENAME=VALUE
name="amanda"
endpoint_type="dgram"
proto="udp"
isrpc=FALSE
wait=TRUE
exec="/local/amanda/amanda/libexec/amanda/amandad
-auth=bsdtcp amdump amindexd amidxtaped"
I am trying to install amanda-3.1.1 on a Sun Solaris 10 x86 host.
I have been running amanda 2.6.1p2 with auth=bsd and -with-user=amanda. This
ran without any problems.
I decided to upgrade to amanda.3.1.1, and decided to change the configure to
auth=bsdtcp, and --with-user=amandabackup.
I ha
