On Wednesday 22 October 2003 05:23, Lucio wrote:
>> >Are you telling me that this is a known problem of 2.4.3?
>> >
>> >It's a production system, I'm afraid it's quite a risk to update
>> > a rpm by compiling from source (especially for an amanda newbie
>> > like me). I'm going to do this only if I have no other chance.
>>
>> I don't blame you for being a bit reticent, it can bite you. And,
>> its for that reason that I don't personally recommend using the
>> rpm's, ever.
>
>[...]
>
>> ISTR I had some sort of a problem, the details of which I can't
>> recall now, and that it was fixed the next day, back someplace in
>> the 2.4.3 tree. ISTR there was a typo in the source, and it made
>> it into the rpm somehow.
>
>Am I the only one here who uses the Amanda version 2.4.3 bundled
> with RH9? If not, and if this is a known problem of that version,
> there must be someone else here experiencing the same
> difficulties... and maybe he/she has already found the solution. I
> believed RedHat was widespread enough.
Download the tarball and read the ChangeLog, paying attention to those
dates in the weeks prior to the redhat 9 release for the final word.
I could be mistaken, and have been before and probably will be again.
:)
Those of us who use it everyday, and offer our support (such as it is)
to other users on this list are often surprised at the amount of
jurassic dust on the versions that somehow manage to ship with the
major distros. Even more amazing is the difficulty in getting the
distros to issue an updated package.
This is for the most part, an entirely user supported software
package, with only occasional input from the currently active
authors, who understandably have other, paycheck related duties to
take care of and have no real desire to spend what little spare time
they may be able to squeeze out of a days work in hand-holding the
amanda users.
We will, because we think amanda is a "choice lady", try and figure
out any problems presented to the group, and each of us has developed
his or her own methods, or specialty areas of expertise. My own
method of choice is to stay current by building each new snapshot so
that if there is a problem that effects how it runs in my personal
configuration, I may already be aware of it by the time someone posts
a problem. That of course depends to an extent on that particular
configuration. As a home user, my 70 real gigs system is of course
smaller than most business systems would be, and the loss of one
backup does not to me, represent a potential loss in cash flow.
The point I was trying to make is that 2.4.3 is getting close to a
year old, and some features have been added, and a few bugs fixed in
the elapsed time since 2.4.3 was current. We on this mailing list
generally see that as a plus, and I'll repeat once again that staying
current has not, by itself, cost me any lost data in maybe 3.5 years
time since I started useing amanda. Thats not to say I haven't lost
a tape or 6 (DDS2's are cheap and you really DO get what you pay for)
or made my own stupid mistakes. But the mistakes or errors were mine
or my hardware's, not amanda's.
FWIW, amanda has maintained backwards compatibility between all
versions since well before I started using it, so it is not required
that you update all clients at the same time as the server if those
logistics are concerning you.
Achieving that long term compatibility is far more related to useing a
consistent configuration script such as the one I posted to show the
framework, than it is to the version of amanda running on machine
so-and-so. Thats why I post it from time to time, often enough I
suppose that some on this list could quote it verbatum from memory!
You can probably look at where the configs, logs and indices are being
kept on your system and adjust that script to make you a build from
the tarball that will go right on top of the older rpm install.
We did at one time have someone subscribed here that was doing the
redhat rpm's, and he would speak up anytime we started to get down on
the rpm vs the tarballs, but he has not made any posts here in many
months now that I'm aware of. I would be nice if he spoke up,
possibly answering your question specificly.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
|
