On Sat, May 25, 2019 at 17:16:55 -0400, Gene Heskett wrote: > On Saturday 25 May 2019 01:21:41 pm Nathan Stratton Treadway wrote: > > > > The Salsa repo is for the official Debian packages. I don't believe > > there is any reason for you to download from it -- you should use the > > Zmanda release tar files (or for bleeding edge, the Zmanda github > > repo) directly. > git clone $$$$$$$$$$ please.
Yes, if you want to be doing the bleeding-edge canary thing, you should be using a clone from the Zmanda github repo. (I believe I saw Chris say that you want to to use the origina/3_5 branch, but I am not sure exactly how the branches-are-currently-branched as far as building non-Debianized builds....) > What I got from github last required i > completely redo my paaswd and group files and still insisted it was > amandabackup. The user and group stuff is controlled at configure/build/install time, not (directly) based on the repo you pull from. So I think the reason you had those passwd/group troubles before was that you followed the instructions for building the Zmanda .deb files (and then installed them), rather than using your gh.cf script to build the just-checked-out source code as you had previously done. > I just checked the first client machine and there is only backup in > either group or passwd. So there's never been an amandabackup on those > wheezy nachines, Thats straight debian built clients, right straight > from the debian repos. Yes, if you use the official Debian repos, backup:backup is what you will find. > Thats why this amandabackup as the user was a > total surprise to me. Serves zero useful purpose and breaks > compatibility all over the place. It it definitely not useful for you -- you should avoid building the Zmanda Debian packages. > All the clients use one access > control file the lives in /var/backups/.amandahosts and is softlinked > to /etc/amandahosts. And contains: > > localhost root amindexd amidxtaped > coyote.coyote.den amanda amdump > > Basicly telling that client the the server known as coyote.coyote.den has > rights to run the client software named in order to do the backup. And > its been that way for close to a decade. Right, this is normal for the official Debian packages (which you use on your client machines). On your server machine, though, you should stick to your gh.cf script (which uses user=amanda... and does not produce .deb files); this will result in diffent paths, pemissions, and ownership than what's found on the clients, but will match the way it has been on the server previously. > > The official Debian Amanda packages have always[*] used user=backup, > > group=backup. > > > No they have not! > > The Zmanda Debian packages have always[*] used user=amandabackup, > > group=disk for the Amanda programs (as documented on > No they have not!> > > http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads > >_page ). I'm not sure what you think is true instead... but I am confident that if you want to use the user "amanda" (i.e. to go back to what you have been doing on that server for the past many years) then you will need to avoid building .deb files and instead use your gh.cf script. Nathan ---------------------------------------------------------------------------- Nathan Stratton Treadway - [email protected] - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
