The real question is not why it is the way it is (unless there's one
that prevents it from being changed), but what would it take to change
it to read a config file at runtime instead of it all being compiled in?
Editing a config file to change a path, device, or hostname would be
much easier than
On Wed, Dec 05, 2001 at 04:27:37PM -0500, Joshua Baker-LePain wrote:
>
> In general, installing pre-compiled binaries of amanda is frowned upon for
> exactly this reason -- many settings are specified at compile time. Your
> only option (AFAIK) is to compile amanda with the portrange settings.
Yep...It would be a wise choice to make port-range (and other options, of
course), definable in p.e. amanda.conf.
Otherwise, having precompiled packages is almost useless.
Thanks for your time and attention
PS: Right now i'm going to recompile amanda for about 15 machines... :)
Eric Veldhuyze
On Fri, 7 Dec 2001 at 9:06am, Eric Veldhuyzen wrote
> So please explain to me, what is so great about setting this all at
> compile time instead of in a configuration file so that it can be
> determined at runtime?
I certainly can't give a definitive answer to this. I *can* tell you that
this
On Wed, 5 Dec 2001 at 7:39pm, David Galveias wrote
> 1 ) Replace a tape in a set:
> I have a set of 5 tapes, 24 Gb each. At least that was what i thought i had.
> The last backup i made, i noticed that one of the tapes is just a 8 Gb tape.
> My question is :
> Can i just (force) label a new 24 Gb
Hi there.
I have 2 questions.
1 ) Replace a tape in a set:
I have a set of 5 tapes, 24 Gb each. At least that was what i thought i had.
The last backup i made, i noticed that one of the tapes is just a 8 Gb tape.
My question is :
Can i just (force) label a new 24 Gb tape to replace this tape and
