Hi Niels,
"Niels S. Richthof" <ni...@richthof.de> writes:
> The bacula director configuration file can get very big and messy, especially
> when backing up many clients.
[...]
> 1. Create a new (empty) directory "/etc/bacula/bacula-dir.conf.d/"
> 2. Add the following snipped to "/etc/bacula/bacula-dir.conf":
>
> # Include subfiles associated with configuration of clients.
> # They define the bulk of the Clients, Jobs, and FileSets.
> # Remember to "reload" the Director after adding a client file.
> #
> @|"sh -c 'for f in /etc/bacula/bacula-dir.conf.d/*.conf ; do echo @${f} ;
> done'"
I agree that this is good practice, I myself manage my configurations in
a similar way.
My feeling is that it's up to the local administrator to decide how they
want to manage their configurations and implement it accordingly.
One of the gains from the strategy of configuration directories is that
the main configuration does not need to be touched by the local
administrator and so local configuration changes do not conflict with
updated configuration files that are provided in the packages. In the
case of Bacula, all installations I manage have modified main
configuration files because I deviate from many things that are
configured in the default configuration.
If the main config file would be mostly empty or defaults could be
overridden, I'd be in favour of this change, but as it stands now, I'd
rather leave it to the local admin.
As an aside, I'm aware that getting asked to replace the configuration
files on each update is not handy and finding a solution is on my todo
list.
Regards
Carsten
