On Wed, Jul 13, 2005 at 11:07:25PM +0200, Stefan G. Weichinger wrote:
> Jon LaBadie wrote:
> >On Wed, Jul 13, 2005 at 10:13:04PM +0200, Stefan G. Weichinger wrote:
> >
> >>I would like to have some motivated amanda-hackers who try to move all 
> >>these configure-time-params into amanda.conf ...
> >
> >When this is done, shouldn't the continued paring of amanda.conf
> >include removal of those things not specific config related?
> >Perhaps it is time for a new system-wide config file with
> >the types of parameters of amanda user ...
> 
> Give me more ...
> 
> Let's think something like
> 
> /etc/amanda/amanda.conf
> /etc/amanda/tapetype.conf
> /etc/amanda/config/daily/daily.conf
> /etc/amanda/config/daily/daily.disklist

Along that line, here's an idea: if the parser were to be modified such that
you could redefine something that had already been specified earlier
in the amanda.conf file, the includefile parameter could be used to inherit
a common base amanda.conf and override the things that need to be different.

Some tools, amrecover in particular, could be made to look for the amanda.conf
as $sysconfdir/$config_name/amanda.conf, and if not found then fall back
to $sysconfdir/amanda.conf.  (I'm not sure that behaviour would be appropriate
for most of the server side, though.)