Dean Waldow wrote:
> This discussion relates to a question or an idea for bacula use with
> many clients. For some linux programs, config files are sometimes being
> organized as nested folders. The current method of a single
> configuration file for each (dir, sd, and fd) seems very reasonable.The
> dir.conf file may get pretty big when one would be trying to use bacula
> with 25-50+ clients. However, when the number of clients grows up to
> numbers like suggested above I start to wonder about a folder based
> alternative or an 'include /etc/bacula/dir/jobs/*' idea. Each client
> could have a separate file for it client specific info (job etc...).
> Bacula-dir would read in the standard dir.conf and then append any text
> data in a file in a given or specified folder. Perhaps it is just a
> preference to deal with one big text file or many small text files...
>
> I hate to suggest something I don't have the skills to implement but it
> was something I have been wondering about. Our science dept is thinking
> of using bacula for 40+ faculty computers and that got me wondering.
There is already a facility to include individual per-job files into the
configuration using the @filename syntax, if you want to do it this way.
This ought to meet most inclusion needs.
--
Phil Stracchino [EMAIL PROTECTED]
Renaissance Man, Unix generalist, Perl hacker
Mobile: 603-216-7037 Landline: 603-886-3518
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
