Amanda-Users

Re: Firewall and Portrange Settings

2004-03-17 16:30:04
Subject: Re: Firewall and Portrange Settings
From: "Stefan G. Weichinger" <monitor AT oops.co DOT at>
To: amanda-users AT amanda DOT org
Date: Wed, 17 Mar 2004 22:27:59 +0100
Hi, Joshua,

on Mittwoch, 17. März 2004 at 18:01 you wrote to amanda-users:

JBL> On Wed, 17 Mar 2004 at 10:47am, Barry A. Trent wrote

>> Wouldn't these be more appropriate as run-time
>> options, perhaps in amanda.conf? I'm using pre-packaged builds for

JBL> Yes they would -- patches accepted.  :)  If you look through the list
JBL> archives, you'll find that there is agreement that there is a bunch of
JBL> stuff decided at compile time that shouldn't be, but that it's not really
JBL> all that easy to fix and there's more pressing development issues.

>> several different flavors of Linux and I'd rather not have to
>> compile/maintain a bunch of different executables if I can avoid it.

JBL> A lot of us find it rather easy to admin amanda this way with scripts to
JBL> ease compilation.

>> 2) Is there some way to get a pre-compiled version of amanda to tell
>> me what portrange settings it was compiled with? I know I can observe
>> the sessions on the wire and figure it out that way, but I'm hoping
>> there is an easier way.

JBL> If you look in /tmp/amanda/amandad*debug, recent versions will tell you
JBL> the compile time options.

I know that I am talking from my subjective point of view, but I am
still trying to think objectively:

It is not that difficult to maintain AMANDA by compiling it from the
sources. If you have once defined your configure-options and put it
into a shell-script, upgrading to a new release is no more than

# cd <new-amanda-sources>; my-config.sh; make
# cd <current-amanda-sources>; make uninstall
# cd <new-amanda-sources>; make install

As new releases or even snapshots of AMANDA compile clean on most
platforms (thanks to the maintainers), there is no more effort needed.

I do this all the time since I-don't-know-when and I don't see the
advantage of applying rpms, that have been pre-compiled by some
distro-maintainer, whose job is to stay "compatible".

(You ask how to figure out which portrange settings a precompiled
version uses. Why not put less energy into setting them yourself?)

---

By compiling your own binaries you get the freedom to choose YOUR own
setup, to set YOUR firewall-settings, to assure that YOUR version of
AMANDA does exactly the job you want it to.

And it stays YOUR setup with each new release of AMANDA.

All this with a small shell-script.

I think this is worth the effort of figuring out the
configure-options.

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:monitor AT oops.co DOT at