-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Stefan,
I hope, you don't mind, that I share this your important hints also with the mailinglist. Am 26.08.2016 um 00:45 schrieb Stefan Klatt: > Hi Jörg, > > I work with the actual betas thank you for using and testing the nightly builds! > and found one point with the new configuration schema: > > If you install Bareos, it creates a set of default configuration > files. That's really good to begin with bareos. > > But if you work with your own file names like "servername-fd.conf" > and not "bareos-fd.conf" and you delete the file "bareos-fd" it > will be new generated if you run an update of Bareos. That's really > bad, every time after an update Bareos doesn't work any more :-( As > a workaround I truncate the not needed files with an "#" in it. That absolutely true, and it is even documented (since beginning of this week), see http://doc.bareos.org/master/html/bareos-manual-main-reference.html#Subd irectoryConfigurationScheme, Resource file conventions, Disable/remove configuration resource files. While I agree, that this is an unwanted effect, it got the benefit, that you can check in your running system if a resource config file come from a bareos package and is it modified (when using rpm packages). When this feature is wanted (I like it), you get the described effects. > I think it's better to generate only the standard directories > without files and a default set of configuration files with a > little documentation in an extra example directory structure. The other feature is, that subpackages can bring additional configuration, like tape backend, webui and others. When this feature is wanted, your approach unfortunately do not work. You see, there is a trade-off between the positive and negative effects. > One other questions... what's the reason for the directory > "bareos-dir-export"? When using the new bconsole command "configure add client ...", it creates the client resource file for the director. However, it also creates the director resource for the corresponding bareos-fd. So configure add client name=client2−fd address=192.168.0.2 password=secret creates /etc/bareos/bareos-dir.d/client/client2-fd.conf (which is automatically loaded into the director) and /etc/bareos/bareos-dir-export/client/client2-fd/bareos-fd.d/director/bar eos-dir.conf (which you have to manually transfer to the corresponding system client2 . regards, Jörg - -- Jörg Steffens [email protected] Bareos GmbH & Co. KG Phone: +49 221 630693-91 http://www.bareos.com Fax: +49 221 630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, Jörg Steffens, P. Storz, M. v. Wieringen -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJXwDYeAAoJENE++pz84GWuk6MQAJRMHjjrwVytYE2x2mh1zFyT YKoirtsIcveatlN59CKshPI46TzjZcCKT+9+8enMjaUitvnSzyRnBDSMKlvM4RNO dIzaw3cdbq/ZCzOougtUTJnND1Al7ZNDbEAvHDbNcc1O80CrpZG2X4JUnDkABZs8 W0P2Gl3fE0rdy3mxlDBewFbRce9HIINDTxsGujSgv/w2KxkdWV4owCZsNq/lcmmH fXPj63jliNVlYkZCrZH90bS4z4M6IVfMv1WT0ID4A0evO2y5xxgW1hayCnnkZ2Ol bVym+KCECH6psZtkMm7xWtHEvWithIdG4XpOlUR2NJ5cX7UyJvRCzS40+xXQJQYZ +pexcHCFt5W0bs52lX6PnrS9TF096h/nmHXeFqiN8KeffnvHR6vrDiteWvsFEJu2 329TA/BQRWWwTh2MCKZZZRGtoolKRjkLpbqEYFHvMtjxGZdCoXdXJqxt8raqmvW+ xGGWij+J7e9pbFX0tQmZpNV2hQeUzslaqywGipQF36QnLgudM5pF3TC8AsGgnrWf cD3ZhOOq2Vta4r8YIbe6i4JKhyIPPOm2QCkl2ntBLsulZRbjURu2bUCILLR0GC8H 9xkpzx5+N7lUiAn/VfS4vo21SnicMNpHzS2+iqSOd/ilFdpjX7JLgcxJootkd51P AzvWDRsvhcWEeWlVz/3X =x3Y1 -----END PGP SIGNATURE----- -- 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.
