> I have no problems with putting the bacula conf files in to the database > if > someone wants to do so. However, I don't foresee any change in the ASCOO > format that Bacula requires -- i.e. I don't foresee Bacula reading its > conf > file directly from an SQL database.
Fair enough. Thinking out loud about how to implement this: would you consider a directive that specified a script to be run whenever a Bacula component needed to open or reference the config file that would supply the name of a file to read for the information? The idea would be similar to the pre-run script for the FD, but applied to the Bacula daemons, and invoked as part of the read-config-file step. That way, the "official" location for the config file could contain only the information to find the config-generator script, and a directive to activate the "dynamic config" option. That config file could trivially be replicated for systems with the ability to do substantial R/O sharing of filesystems. ------------------------------------------------------------------------- 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
