Last night I upgraded my Bareos director and storage daemons from 19.x to
21.x using the binary packages published on FreeBSD's repositories (i.e.
not the ones on download.bareos.org).
Unfortunately, the package installs a default "sample" configuration.
Moreover, these sample entries are live, i.e. they will be read and acted
upon when bareos-{dir,fd,sd} are launched. While the package doesn't
overwrite any existing active config, it will add sample entries to it. In
a Bareos config directory tree, it can take considerable work to find and
remove these entries.
The Debian packages for bareos-filedaemon and bareos-tray-monitor do the
same thing. When I upgraded the installation on my Linux desktop from
v17(!) to v22, it added a new, active entry to the config:
/etc/bareos/tray-monitor.d/client/FileDaemon-local.conf, which I had to
manually delete.
I respectfully submit it should not be doing this. All the package should
be installing are inactive, sample entries. Bareos is particularly
complicated to configure, and I would venture to say there's no such thing
as a "typical" installation. Every Bareos installation is highly
customized. Dance on the sample files all you like, but don't modify/add
to the active config; it just complicates the upgrade process.
Schwab
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/cffec05e-8df9-43f9-884b-a9cc2ff5b175n%40googlegroups.com.
