Bug 18322
Summary: | Amanda client problems | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jim Simmons <simmonsjw> |
Component: | amanda | Assignee: | Trond Eivind Glomsrxd <teg> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | dr, j, rupa+bugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-01-04 23:34:27 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jim Simmons
2000-10-04 12:29:05 UTC
All but changing the operator home directory are fixed in amanda-2.4.2-0.19991216beta1.1. the amanda operator home dir is another slight problem if you already have an .amandahosts file - b/c it runs as a script to update that file you run the risk of munging the hell out of it. make it an actual file so in the event it installs it can be saved as a .rpmsave or a .rpmnew otherwise you end up with a kludged file - and on the client as well. your best bet is to leave .amandahosts alone and not add anything to it. All of this should be fixed in amanda 2.4.2-2, coming soon to a rawhide near you. I've "fixed" this by: 1) ensuring operator is in the "root" group (it should be) 2) making sure /root is g+rx 3) adding the line "groups = yes" for /etc/xinetd.d/amanda (and other amanda services). This tells xinetd to give the service all supplemental groups for the user specified. Now, since /root is g+rx, the service can read the .amandahosts file. Having an "amanda" user is probably optimal, but the above is a nice quick workaround. A amanda user was added in the RPMs I referred to |