openbsd-ports/sysutils/bacula/patches/patch-src_qt-console_bat_conf_in

$OpenBSD: patch-src_qt-console_bat_conf_in,v 1.2 2009/10/02 02:34:05 merdely Exp $
--- src/qt-console/bat.conf.in.orig	Thu May 14 12:06:41 2009
+++ src/qt-console/bat.conf.in	Tue Sep  1 22:31:52 2009
@@ -5,6 +5,6 @@
 Director {
   Name = @basename@-dir
   DIRport = @dir_port@
-  address = @hostname@
+  address = 127.0.0.1
   Password = "@dir_password@"
 }
Update bacula to 3.0.2: * Shared objects * Virtual backups * Duplicate Job Control * TLS Authentication * Exclude Dir Containing = <filename-string> * Plugins including Exchange 2003/2007 Plugin * libdbi backend abstraction * Bat enhancements Upgrading from 2.4.4 to 3.0.2 requires updating the database using /usr/local/libexec/bacula/update_bacula_database. Database upgrades from older databases can be done with other scripts in /usr/local/libexec/bacula/updatedb. You can determine your database version in mysql and postgresql with 'select * from version'. As sthen@ reminded me and the documentation points out, when upgrading between major versions (2.x.x -> 3.x.x), you should upgrade all of your components at the same time due to protocol changes. a lot of help from and ok sthen@ 2009-10-01 22:34:05 -04:00			$OpenBSD: patch-src_qt-console_bat_conf_in,v 1.2 2009/10/02 02:34:05 merdely Exp $
			`--- src/qt-console/bat.conf.in.orig Thu May 14 12:06:41 2009`
			`+++ src/qt-console/bat.conf.in Tue Sep 1 22:31:52 2009`
			`@@ -5,6 +5,6 @@`
Update bacula to 2.2.8. Bacula changelog: http://bacula.svn.sourceforge.net/viewvc/bacula/branches/Branch-2.2/bacula/ChangeLog?revision=6309&view=markup Major port change in this version: -main subpackage is now bacula-client -server subpackage remains bacula-server -bat subpackage is new bacula admin tool -client subpackage goes away. If the old -main subpackage was installed, the upgrade path is to install both bacula-client and bacula-server. Lots of input and assistance from sthen and okan. ok okan; "if it works for you, go for it" sthen 2008-02-06 21:53:35 -05:00			`Director {`
Update bacula to 3.0.2: * Shared objects * Virtual backups * Duplicate Job Control * TLS Authentication * Exclude Dir Containing = <filename-string> * Plugins including Exchange 2003/2007 Plugin * libdbi backend abstraction * Bat enhancements Upgrading from 2.4.4 to 3.0.2 requires updating the database using /usr/local/libexec/bacula/update_bacula_database. Database upgrades from older databases can be done with other scripts in /usr/local/libexec/bacula/updatedb. You can determine your database version in mysql and postgresql with 'select * from version'. As sthen@ reminded me and the documentation points out, when upgrading between major versions (2.x.x -> 3.x.x), you should upgrade all of your components at the same time due to protocol changes. a lot of help from and ok sthen@ 2009-10-01 22:34:05 -04:00			`Name = @basename@-dir`
Update bacula to 2.2.8. Bacula changelog: http://bacula.svn.sourceforge.net/viewvc/bacula/branches/Branch-2.2/bacula/ChangeLog?revision=6309&view=markup Major port change in this version: -main subpackage is now bacula-client -server subpackage remains bacula-server -bat subpackage is new bacula admin tool -client subpackage goes away. If the old -main subpackage was installed, the upgrade path is to install both bacula-client and bacula-server. Lots of input and assistance from sthen and okan. ok okan; "if it works for you, go for it" sthen 2008-02-06 21:53:35 -05:00			`DIRport = @dir_port@`
			`- address = @hostname@`
			`+ address = 127.0.0.1`
			`Password = "@dir_password@"`
			`}`