On 07/07/17 08:01, Kern Sibbald wrote: > > Release 9.0.0 > > I am pleased to announce that we have just released Bacula version 9.0.0.
One question on building Bacula 9 (on Solaris 10, but I don't think that matters). It's possible this question has been answered in the past and I've just forgotten the answer. The only daemon that actually talks to the database is the Director. But when if I configure with --disable-build-dird, configuration fails unless I specify a DB engine. I no longer have a DB engine installed on the SAN that runs my disk-based SD because that server's job is now ONLY, SOLELY AND UNIQUELY to serve SAN and run the disk SD. I presume the reason for this is because the storage daemon tools such as bscan may need access to the database. Is there any way I can tell Bacula to build the storage daemon with no tools, just the daemon itself? I don't see a --disable-build-tools configure option, and I don't really want to reinstall a set of DB client libraries that will never be used. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
