From eb85da0842304d6a13b40212483cac59279390b1 Mon Sep 17 00:00:00 2001
From: Kern Sibbald <kern@sibbald.com>
Date: Mon, 13 Oct 2008 19:41:11 +0000
Subject: [PATCH] Update

---
 docs/manuals/en/concepts/concepts.kilepr |  4 +-
 docs/manuals/en/concepts/newfeatures.tex | 54 +++++++++++++++++++-----
 2 files changed, 46 insertions(+), 12 deletions(-)

diff --git a/docs/manuals/en/concepts/concepts.kilepr b/docs/manuals/en/concepts/concepts.kilepr
index f9357969..1c58c86b 100644
--- a/docs/manuals/en/concepts/concepts.kilepr
+++ b/docs/manuals/en/concepts/concepts.kilepr
@@ -161,10 +161,10 @@ order=-1
 
 [item:newfeatures.tex]
 archive=true
-column=31
+column=12
 encoding=UTF-8
 highlight=LaTeX
-line=148
+line=1697
 open=true
 order=0
 
diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index d6893ecc..c8535c71 100644
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -260,9 +260,9 @@ obey this flag.  The new directive is:
 The default value is {\bf no}.
 
 
-\section{Ignore Dir = \lt{}filename-string\gt{}}
+\section{Exclude Dirs Containing = \lt{}filename-string\gt{}}
 \index[general]{IgnoreDir}
-The {\bf Ignore Dir = \lt{}filename\gt{}} is a new directive that can be added to the Include
+The {\bf ExcludeDirsContaining = \lt{}filename\gt{}} is a new directive that can be added to the Include
 section of the FileSet resource.  If the specified
 filename is found on the Client in any directory to be backed up, 
 the whole directory will be ignored (not backed up).
@@ -277,7 +277,7 @@ For example:
         signature = MD5
       }
       File = /home
-      IgnoreDir = .excludeme
+      Exclude Dirs Containing = .excludeme
     }
   }
 \end{verbatim}
@@ -485,22 +485,22 @@ default Exchange installation.
 \subsection{Backup up}
 
 To back up an Exchange server the Fileset definition must contain at
-least 'Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"' for
+least {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"} for
 the backup to work correctly. The 'exchange:' bit tells Bacula to look
 for the exchange plugin, the '@EXCHANGE' bit makes sure all the backed
 up files are prefixed with something that isn't going to share a name
 with something outside the plugin, and the 'Microsoft Information Store'
 bit is required also. It is also possible to add the name of a storage
-group to the 'Plugin =' line, eg 'Plugin =
-"exchange:/@EXCHANGE/Microsoft Information Store/First Storage Group"'
+group to the "Plugin =" line, eg \\
+{\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store/First Storage Group"} \\
 if you want only a single storage group backed up.
 
 Additionally, you can suffix the 'Plugin =' directive with
-':notrunconfull' which will tell the plugin not to truncate the Exchange
+":notrunconfull" which will tell the plugin not to truncate the Exchange
 database at the end of a full backup.
 
 An Incremental or Differential backup will backup only the database logs
-for each Storage Group by inspecting the 'modified date' on each
+for each Storage Group by inspecting the "modified date" on each
 physical log file. Because of the way the Exchange API works, the last
 logfile backed up on each backup will always be backed up by the next
 Incremental or Differential backup too. This adds 5MB to each
@@ -1073,9 +1073,9 @@ typedef struct s_baculaFuncs {
        int type, time_t mtime, const char *fmt, ...);
    bRC (*DebugMessage)(bpContext *ctx, const char *file, int line,
        int level, const char *fmt, ...);
-   void *(*malloc)(bpContext *ctx, const char *file, int line,
+   void *(*baculaMalloc)(bpContext *ctx, const char *file, int line,
        size_t size);
-   void (*free)(bpContext *ctx, const char *file, int line, void *mem);
+   void (*baculaFree)(bpContext *ctx, const char *file, int line, void *mem);
 } bFuncs;
 \end{verbatim}
 
@@ -1666,4 +1666,38 @@ should return:
   
 \end{description}
 
+\section{Bacula Plugin Entrypoints}
+When Bacula calls one of your plugin entrypoints, you can call back to
+the entrypoints in Bacula that were supplied during the xxx plugin call
+to get or set information within Bacula.
 
+\subsection{bRC registerBaculaEvents(bpContext *ctx, ...)}
+This Bacula entrypoint will allow you to register to receive events
+that are not autmatically passed to your plugin by default. This 
+entrypoint currently is unimplemented.
+
+\subsection{bRC getBaculaValue(bpContext *ctx, bVariable var, void *value)}
+Calling this entrypoint, you can obtain specific values that are available
+in Bacula.
+
+\subsection{bRC setBaculaValue(bpContext *ctx, bVariable var, void *value)}
+Calling this entrypoint allows you to set particular values in
+Bacula.
+
+\subsection{bRC JobMessage(bpContext *ctx, const char *file, int line,
+       int type, time\_t mtime, const char *fmt, ...)}
+This call permits you to put a message in the Job Report.
+
+
+\subsection{bRC DebugMessage)(bpContext *ctx, const char *file, int line,
+       int level, const char *fmt, ...)}
+This call permits you to print a debug message.
+
+
+\subsection{void bMalloc(bpContext *ctx, const char *file, int line,
+       size\_t size)}
+This call permits you to obtain memory from Bacula's memory allocator.
+
+
+\subsection{void bFree(bpContext *ctx, const char *file, int line, void *mem)}
+This call permits you to free memory obtained from Bacula's memory allocator.
-- 
2.39.5