Hey Chris, Here is another link to people having problems with this: http://adsm.org//lists/html/Amanda-Users/2009-05/msg00098.html
Given that Debian and Ubuntu package amanda with a backup user of "backup" instead of "amandabackup", shouldn't there be a serverside bsdtcp option for controlling which username the server authenticates as to the client? I looked through the bsdtcp code in the repo, but I couldn't find where the relevant block of code is. If someone who knows the source better than me could point me in the right direction, I could submit a patch. Joel Eidsath On Fri, Jul 22, 2011 at 1:13 PM, Alden Timme <alden.ti...@gmail.com> wrote: > > > ---------- Forwarded message ---------- > From: Alden Timme <alden.ti...@gmail.com> > Date: Thu, Jul 21, 2011 at 3:51 PM > Subject: Re: Zmanda Windows Client with dumpuser other than "amandabackup" > To: Chris Nighswonger <cnighswon...@foundations.edu> > Cc: Paddy Sreenivasan <pa...@zmanda.com>, amanda-users@amanda.org > > > OK I guess it is what it is... Maybe a patch will come out at some point. > Thanks for the responses, though. > > On Thu, Jul 21, 2011 at 3:20 PM, Chris Nighswonger > <cnighswon...@foundations.edu> wrote: >> >> Hi Alden, >> >> On Thu, Jul 21, 2011 at 5:25 PM, Alden Timme <alden.ti...@gmail.com> >> wrote: >>> >>> Is there really no other way for the backup to work? I.e. something like >>> being able to set "client_username" as you can with rsh or ssh >>> authentication? >> >> The truth of the matter is that ZWC is a proprietary product which is >> close sourced. Thus as long as the code owner elects not to invest the time >> to add the ability to set the username at install time or in a config file, >> we are stuck with the registry hack mentioned in the wiki. >> >> This is another case-in-point for open source code. >> >> Kind Regards, >> Chris > > >
