Jörg Steffens <[email protected]> writes: > As an administrator you still got the chance to disable this behavior, > by using a non-default Bareos configuration directory (either change the > service file or create a /etc/bareos/bareos-dir.conf with following > content: @/etc/my-bareos-config/bareos-dir.d/*/*.conf). > > Anyhow, of course we like to implement what all (or at least) most > people want. As said, in the past, I heard several persons wanting the > feature as implemented right now. > Anybody else with an opinion on this?
I like the new scheme, although I will not use it myself since I manage clients and jobs via Puppet. however, it is annoying that when I do "make install" from the git master, I get a lot of gunk in /etc/bareos. it would be nice if configure had a switch to disable the installation of default configuration, or even better, if it installed it to "$docdir/example-config/" and left it completely up to packagers what to put in "/etc/bareos". FWIW, I currently use these path related settings with configure: ./configure --prefix=/opt/bareos --with-confdir=/etc/bareos --with-scriptdir=/etc/bareos/distscripts (the latter setting helps a lot, and I certainly don't want my finely tuned query.sql to be garbled after each make install ;) -- Kjetil T. Homme Redpill Linpro AS - Changing the game -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
