On Nov 5, 2008, at 5:35 PM, Mark V wrote: > On Thu, Nov 6, 2008 at 1:37 AM, Steve Thompson <[EMAIL PROTECTED]> > wrote: >> On Tue, 4 Nov 2008, John Drescher wrote: >> >>>> Converting it to an XML file would not pose the problems >>>> specified in >>>> the above wiki, there are lots of tools to create/parse XML files >>>> tha >>>> could be useful. >>>> >>> I would vote against this if I could. I mean this will make it >>> harder >>> for me to edit the configuration files through ssh and to me any gui >>> tools to edit the files will just get in the way being that I have >>> 40+ >>> clients and about 75 different jobs. >> >> I also strongly vote against this, for the same reasons. >> > > I'm strongly against XML config files. > > I'm also strongly against moving Bacula configuration details/data out > of simple text files, and further complicating configuration storage > or generation of a configuration file. I'm against this whether one > proposes the use of a DB, Augeas, Puppet or whatever the next > 'you-beaut-thing' is :)
I agree. However, using an optional 'third-party' tool is quite acceptable to all. I refer here to Fruity and Nagios. The use of Fruity is optional. It produces plain text configuration files to be used by Nagios. That is the approach I would endorse for Bacula should anyone desire to code such a beast. -- Dan Langille http://langille.org/ ------------------------------------------------------------------------- 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
