> > The design of a GUI for bacula may revolve arround interfacing with > > the dameons. I was wondering > > if just designing a GUI for config file modification might simply > > suffice, i.e. a config file editor with > > the smarts of syntax checking and linking of all the resources in > > the main bacula-dir.conf file. > > Most of the cfg files do not change much or at all. The file most > > often modified is the bacula-dir.conf > > It would much easier to just concentrate on that task rather than > > designing a GUI which interacts with the > > dir daemon.
I'd rather see a majority of the configuration moved into database tables. As more organizations move towards a configuration management database approach (CMDB), controlling configuration is going to be more important and more complex. Flat files are nice from a simplicity point of view, but the syntax is becoming complex enough that it might be smarter (and easier to maintain across multiple systems) to normalize it and move it into a RDBMS. It would also allow real-time updates more easily. Maybe the easy approach would be to write a tool to maintain the configuration in the database, and then auto-generate the appropriate files from the database tables. ------------------------------------------------------------------------- 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
