Dan Langille <[EMAIL PROTECTED]> writes: > I know of another project that does something similar. Nagios. > > Nagios has a sister project, Lilac (previously called Fruity). > Fruity is a web-based interface for maintaining your Nagios > configuration files. It is quite good. You export your > Fruity/Lilac database into Nagios configuration files.
how about the other way around? I really like version control on all configuration files, so such a solution needs to be two-way. > If anyone were to go this route, I'd recommend they look closely at > how Lilac/Nagios interact and proceed in a similar fashion. Moving > to XML for the main configuration files is ill-advised. another approach is to write an Augeas lens for the Bacula configuration. it may be necessary/useful to restrict the Bacula syntax somewhat, e.g., require users to remove the optional spaces in directives. -- regards, | Redpill _ Kjetil T. Homme | Linpro (_) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
