On Apr 26, 2007, at 4:41 PM, Dan Langille wrote: > Fruity is the configuration tool for Nagios. I suggest that such a > tool for Bacula would be useful too. > > However, all configuration files should be plain text. Much like > what Fruity does.
Unlike Nagios, Bacula already has an include directive. (Nagios has templates--which are not in fact consistent across all classes of configuration objects, which is very annoying.) This makes it a lot easier (I rolled something of my own kinda like Fruity); on my Bacula setups I have separate job, client, and fileset subdirectories. In bacula-dir.conf, I just have @/etc/bacula/jobs/ machinename and @/etc/bacula/filesets/genericfilesetname. Each job has its own client inclusion, and if the job needs a fileset that isn't generic, it gets a specific fileset inclusion too. It's very easy to write a short tool to generate these configs, and the only modification I ever really need to do is to do one-off filesets for clients with weird disk layouts. Adam ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
