On Sat, May 25, 2019 at 21:38:39 -0400, Gene Heskett wrote:
> Same install dvd for 4 of them because this machines wheezy install was
> also done with that same dvd. 4 different passwd and group settings, yet
> it all just worked.
These differences simply show that you used different methods (offical
Debian v.s. Zmanda Debian v.s. non-Debianianized-build, etc.) to install
Amanda on those various machines.
This is perfectly fine; the hard rules Amanda has about user/group
ownership etc. are specific to each machine, so you can mix-and-match
across machines just fine.
What you want to avoid doing is changing paradigms on a particular box
(and especially not on the server) -- and thus the need to be sure to
stick with your own build script on your server.
(Note that the "backup" user and groups, UID/GUI 34, are included in the
base Debian install, so they will exist on _all_ Debian machines -- while
"amanda" or "amandabackup" must have been created sometime after the
initial installation, either manually or as part of a .deb-package
installation script.)
>
> Now I think I have all the clients but this machine working, so maybe its
> time to go see what I have to do to my passwd and group files to make
> 3.5.1, built with my script, just work. Then incorporate those changes
> into GenesAmandaHelper and make that work, making it version 0.62, too.
"Coyote" is your Amanda server, right? Is that the system you are
referring to ("this machine") here? (If you have problems with some
other client, that's a separate issue and should probably be in its own
thread.)
Unless you deleted the "amanda" user recently, you should not have to
change anything in passwd or group to get back to using your
script-build binaries.
If you changed ownerships of some files or directories while trying to
get the package-installed version working, those will probably need to
be changed back to "amanda" (i.e. restored to the way they were).
> The zmanda copy was last touched 6 months ago according to git. And only
> came as a tar.zip.
>
> So where do I get a tarball that incorporates the work done here over the
> last couple months?
(You should make sure you get back to a working system [i.e. resolving
all permission/ownership problems] using what you have built from
previously, before trying to switch to something new.)
There hasn't been a "release" since 3.5.1, so there are no release
tarballs that have anything newer than that.
You can pull a tarball down from github, but off hand I don't believe
that will be more convienient than building from a local git checkout.
However, as far as I can tell, there hasn't been any
actually-interesting changes committed to the repo since the 3.5.1
release. (What has been committed is the mentioned-on-this-list
packaging changes for RPM and Debian, which don't apply to you, plus a
few other minor changes which don't seem interesting either.... )
But if you are ready to try building from the repo (in preparation for
the time in the hopefully-near future when there are interesting changes
there), you would follow the instructions in Chris's 9 May 2019 message,
e.g.
$ cd <your-Zmanda-github-repo-clone-directory>
$ git checkout -b 3_5mine origin/3_5
(this checks out the origin/3_5 branch, at the same time creating a
local branch called "3_5mine"; you can pick a different name if you
like. The idea is that you want to be working in a locally-named branch
so that any changes you make to files while you are workingcan be saved
to that branch, separate from the upstream branch.)
Then, from that checkout directory, run your gh.cf script to kick off
the build (first making sure the --with-security-file= line is what you want
it to be)... and see what happens....
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
