Fix bug #2240 correct typo and directive default

[bacula/docs] / docs / manuals / en / main / newfeatures.tex

diff --git a/docs/manuals/en/main/newfeatures.tex b/docs/manuals/en/main/newfeatures.tex
index 965868ffb4f5380e4db2cf56f0f2aeec8ba14b98..77e6068f89da0be55142e601590eee78f2106e32 100644 (file)
--- a/docs/manuals/en/main/newfeatures.tex
+++ b/docs/manuals/en/main/newfeatures.tex
@@ -1,4 +1,7 @@
 \chapter{New Features in 9.0.0}
+Note: The first beta versions are released as version 7.9.0, and the first
+production release will be 9.0.0. 
+
 \subsection{Maximum Virtual Full Interval Option}
 Two new director directives have been added:
 
@@ -6,7 +9,7 @@ Two new director directives have been added:
    Max Virtual Full Interval
 and
    Virtual Full Backup Pool
-\end(verbatime)
+\end{verbatim}
 
 The {\bf Max Virtual Full Interval} directive should behave similar to the
 {\bf Max Full Interval}, but for Virtual Full jobs.  If Bacula sees that
@@ -861,6 +864,70 @@ Deduplication Optimized Volumes whitepaper.
 This feature is available if you have Bacula Community produced binaries
 and the Aligned Volumes plugin.
 
+\subsection{New Message Identification Format}
+We are starting to add unique message indentifiers to each message (other
+than debug and the Job report) that Bacula prints.  At the current time
+only two files in the Storage Daemon have these message identifiers and 
+over time with subsequent releases we will modify all messages.
+
+\smallskip
+The message identifier will be kept unique for each message and once
+assigned to a message it will not change even if the text of the message
+changes.  This means that the message identifier will be the same no matter
+what language the text is displayed in, and more importantly, it will allow
+us to make listing of the messages with in some cases, additional
+explanation or instructions on how to correct the problem.  All this will
+take several years since it is a lot of work and requires some new programs
+that are not yet written to manage these message identifiers.
+
+\smallskip
+The format of the message identifier is:
+
+\begin{verbatim}
+   [AAnnnn]
+\end{verbatim}
+where A is an upper case character and nnnn is a four digit number, where
+the first charcter indicates the software component (daemon); the second
+letter indicates the severity, and the number is unique for a given
+componet and severity.
+
+\smallskip
+For example:
+
+\begin{verbatim}
+   [SF0001]
+\end{verbatim}
+
+The first charcter representing the componend at the current time one of
+the following:
+
+\begin{verbatim}
+   S      Storage daemon
+   D      Director
+   F      File daemon
+\end{verbatim}
+
+\smallskip
+The second character representing the severity or level can be:
+
+\begin{verbatim}
+   A      Abort 
+   F      Fatal
+   E      Erropr
+   W      Warning
+   S      Security
+   I      Info
+   D      Debug
+   O      OK (i.e. operation completed normallly)
+\end{verbatim}
+
+So in the example above [SF0001] indicates it is a message id, because of
+the brackets and because it is at the beginning of the message, and that
+it was generated by the Storage daemon as a fatal error.
+\smallskip
+As mentioned above it will take some time to implement these message ids
+everywhere, and over time we may add more component letters and more
+severity levels as needed.
 
 
 \chapter{New Features in 7.4.0}
@@ -2415,8 +2482,8 @@ especially useful for specifying more complicated Migration/Copy SQL
 statements and in creating long restricted console ACL lists.
 
 \subsection{Maximum Spawned Jobs}
-The Job resource now permits specifying a number of {\bf Maximum Spawn
-Jobs}. The default is 300.  This directive can be useful if you have
+The Job resource now permits specifying a number of {\bf Maximum Spawned
+Jobs}. The default is 600.  This directive can be useful if you have
 big hardware and you do a lot of Migration/Copy jobs which start
 at the same time.  In prior versions of Bacula, Migration/Copy
 was limited to spawning a maximum of 100 jobs at a time.