On Monday 29 October 2007 21:53, Scott Barninger wrote: > Hello Kern, > > I just now replaced my bacula-mysql with bacula-sqlite on my EL3 server > because I wanted to get away from the limitations on nested queries. In > the process I note 2 bugs, one in the spec file and one in bat.
If you are moving up (rather down) to SQLite, I would suggest that it would be best to use SQLite3 because SQLite2 is no longer developed by the author and may not be supported by Bacula much longer. Is there any reason why you don't build a more recent version of MySQL from source? It really is not too hard to do and is documented in the manual. The advantage (though it may be too late) is that you could probably quite easily continue to use the same catalog (just export it then reimport it). > > The spec file bug is that I am installing /var/lib/bacula/bacula.db with > ownership root.root rather than bacula.bacula. Thus the director is > unable to access the catalog. Can't understand why this never got > reported. I will fix this for 2.2.6. I suspect that very few users are using SQLite these days since the manual now recommends against using it in production. > > The bat bug is that when clicking the button for messages it injects the > command .messages rather than messages into the console window. Yes, I see you found later that it is OK as a dot command -- the dot commands are designed for gui programs ... Regards, Kern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
