+Kern;;;2007/19/11;;15:25
+Bacula version 2.2.5 source tar files as well as the Win32
+binaries are available in the Bacula release area of Source Forge.
+
+This release is an important bug fix upgrade to version 2.2.4,
+and we recommend that all users upgrade as soon as possible.
+
+Despite the fact that the Release Notes are rather short, the bug
+fixes represent quite a lot of work:
+
+Version 2.2.5 is a major bug fix release to version 2.2.4
+- It fixes the following bugs: #961, 962, 963, 969, 968, 960,
+ 964, (possibly 935 and 903), 953, 953, 967, 966, 965, 954,
+ 957, 908, 958, and 955.
+- It also improves listing performance problems in bat pointed
+ out by Chris Howells.
+;;;
Kern;;;2007/9/29;;;20:30
I have found and fixed a serious data loss bug in Bacula.
<a href="http://bugs.bacula.org">http://bugs.bacula.org</a>
</p>
-To view the bug reports, you can login as user <b>anonymous</b>
-and password <b>anonymous</b>.
+To view the bug reports, you can login as user <b>anonymous</b> and
+password <b>anonymous</b>. The advantage of actually being subscribed
+is that you will be notified by email of any serious bugs and their
+resolution.
-To submit bug reports, you must create an account. You must also use
-a browser running a US ASCII code page or UTF-8. Some users running
-Win32 IE with Windows Eastern European code pages have experienced
-problems interfacing with the system.
+To submit bug reports, you must create an account. You must also use a
+browser running a US ASCII code page or UTF-8. Some users running Win32
+IE with Windows Eastern European code pages have experienced problems
+interfacing with the system.
<p>
Most Bacula problems are questions of support, so if you are not
sure if a problem you are having is a bug, see the support page
-on this site for links to the email lists.
+on this site for links to the email lists. However, once you have
+determined that a problem is a bug, you must either submit a bug
+report to the bugs database or send an email to the bacula-devel
+list, otherwise it is possible that the developers will never know
+about your bug and thus it will not get fixed.
-You should expect two things to be slightly different in our
-Bugs handling than many other Open Source projects. First, we unfortunately
-cannot supply support via that bugs database, and second, we close
-bugs very quickly to avoid being overwhelmed. Please don't take this
-personally. If you want to add a note to the bug report after it
-is closed, you can do so without reopening the bug. If after everything
-considered, you are convinced there is a bug and you have new information,
-you can always reopen the bug report.
+You should expect two things to be slightly different in our Bugs
+handling than many other Open Source projects. First, we unfortunately
+cannot give support or handle feature requests via the bugs database,
+and second, we close bugs very quickly to avoid being overwhelmed.
+Please don't take this personally. If you want to add a note to the bug
+report after it is closed, you can do so by reopening the bug, adding a
+bug note, then closing the bug report again, or for really simple
+matters, you can send an email to the bacula-devel email list. If a
+developer closes a bug report and after everything considered, you are
+convinced there really *is* a bug and you have new information, you can
+always reopen the bug report.
<h3>Information Needed in a Bug Report</h3>
For us to respond to a bug report, we normally need the following
-as the minimum information, which you can enter into the appropriate
+as the minimum information, which you should enter into the appropriate
fields of the bug reporting system:
<ul>
<li>Your operating system</li>
<li>Have you run the <b>btape</b> "test" command?</li>
</ul>
-The first two of these items can be fulfilled by sending
-us a copy of your <b>config.out</b> file, which is in the
-main <b>Bacula</b> source directory after you have done
-your <b>./configure</b>.
+The first two of these items can be fulfilled by sending us a copy of
+your <b>config.out</b> file, which is in the main <b>Bacula</b> source
+directory after you have done your <b>./configure</b>.
+
<p>In addition, we will sometimes need a copy of your Bacula
-configuration files (especially bacula-dir.conf). If you
-think it is a configuration problem, please don't hesitate
-to send them if necessary.</td>
+configuration files (especially bacula-dir.conf). If you think it is a
+configuration problem, please don't hesitate to send them if
+necessary.</td>
</tr>
<tr>
<td style="font-size: 14px; padding: 0px 20px 0px 20px">
\index[general]{Backing Up Your Bacula Database - Security Considerations }
\index[general]{Database!Backing Up Your Bacula Database - Security Considerations }
-We provide make_catalog_backup as an example of what can be used to backup
+We provide make\_catalog\_backup as an example of what can be used to backup
your Bacula database. We expect you to take security precautions relevant
-to your situation. make_catalog_backup is designed to take a password on
+to your situation. make\_catalog\_backup is designed to take a password on
the command line. This is fine on machines with only trusted users. It is
not acceptable on machines without trusted users. Most database systems
provide a alternative method, which does not place the password on the
command line.
-The make_catalog_backup contains some warnings about how to use it. Please
+The make\_catalog\_backup script contains some warnings about how to use it. Please
read those tips.
To help you get started, we know PostgreSQL has a password file,
projects / bacula / docs / commitdiff
