exceed 4 billion and thus require a 64 bit value.
\item [yes|no]
- \index[dir]{yes|no }
+ \index[dir]{yes or no }
Either a {\bf yes} or a {\bf no}.
\item [
\normalsize
When the job is run, you will get messages from the output of the script stating
that the backup has started. Even though the command being run is
- backgrounded with &, the job will block until the "db2 BACKUP DATABASE" command,
+ backgrounded with \&, the job will block until the "db2 BACKUP DATABASE" command,
thus the backup stalls.
To remedy this situation, the "db2 BACKUP DATABASE" line should be changed to the following:
\label{ConnectionRefused}
\item [In connecting to my Client, I get ''ERR:Connection Refused. Packet
Size too big from File daemon:192.168.1.4:9102`` Why?]
- \index[general]{In connecting to my Client, I get &htmlQuoteERR:Connection Refused.
- Packet Size too big from File daemon:192.168.1.4:9102&htmlQuote Why? }
+ \index[general]{In connecting to my Client, I get ``:Connection Refused.
+ Packet Size too big from File daemon:192.168.1.4:9102'' Why? }
This is typically a communications error resulting from one of the following:
until the first one that matches. Note, if you exclude a directory, no
files or directories below it will be matched.
-\item [exclude=yes|no]}
+\item [exclude=yes|no]
\index[dir]{exclude }
The default is {\bf no}. When enabled, any files matched within the Options
will be excluded from the backup.
violation}{http://www.gnu.org/copyleft/gpl-violation.html}
\item
\elink{Translations of the
- GPL}{http://www.gnu.org/copyleft/copyleft.html#translations}
+ GPL}{http://www.gnu.org/copyleft/copyleft.html\#translations}
\end{itemize}
FSF \& GNU inquiries \& questions to
\elink{gnu@gnu.org}{mailto:gnu@gnu.org}. Other
-\elink{ways to contact}{http://www.gnu.org/home.html#ContactInfo} the FSF.
+\elink{ways to contact}{http://www.gnu.org/home.html\#ContactInfo} the FSF.
Comments on these web pages to
\elink{webmasters@www.gnu.org}{mailto:webmasters@www.gnu.org}, send other
violation}{http://www.gnu.org/copyleft/gpl-violation.html}
\item
\elink{Translations of the
- LGPL}{http://www.gnu.org/copyleft/copyleft.html#translationsLGPL}
+ LGPL}{http://www.gnu.org/copyleft/copyleft.html\#translationsLGPL}
\item The GNU Lesser General Public License as a
\elink{text file}{http://www.gnu.org/copyleft/lesser.txt}
\item The GNU Lesser General Public License as a
FSF \& GNU inquiries \& questions to
\elink{gnu@gnu.org}{mailto:gnu@gnu.org}. Other
-\elink{ways to contact}{http://www.gnu.org/home.html#ContactInfo} the FSF.
+\elink{ways to contact}{http://www.gnu.org/home.html\#ContactInfo} the FSF.
Comments on these web pages to
\elink{webmasters@www.gnu.org}{mailto:webmasters@www.gnu.org}, send other
\item [The Bacula Events Class]
You create this class in the startup script, and you pass
- it to the Bacula Object's {\bf set_events} method. The
+ it to the Bacula Object's {\bf set\_events} method. The
purpose of the Bacula Events Class is to define what global
or daemon events you want to monitor. When one of those events
occurs, your Bacula Events Class will be called at the method
You create this class in the JobStart method of your Bacula Events
class, and it allows you to define which of the possible Job Object
events you want to see. You must pass an instance of your Job Events
- class to the Job Object set_events() method.
+ class to the Job Object set\_events() method.
Normally, you will probably only have one
Job Events Class, which will be instantiated for each Job. However,
if you wish to see different events in different Jobs, you may have
The first thing the startup script must do is to define what global Bacula
events (daemon events), it wants to see. This is done by creating a
Bacula Events class, instantiating it, then passing it to the
-{\bf set_events} method. There are three possible
+{\bf set\_events} method. There are three possible
events.
\begin{description}
Here, your JobEvents class method NewVolume will be called each time
the Job needs a new Volume name. To actually register the events defined
in your class with the Job, you must instantiate the JobEvents class and
-set it in the Job {\be set_events} variable. Note, this is a bit different
+set it in the Job {\bf set\_events} variable. Note, this is a bit different
from how you registered the Bacula events. The registration process must
be done in the Bacula JobStart event (your method). So, you would modify
Bacula Events (not the Job events) as follows:
The following are the methods (subroutines) provided within the
directory by the {\bf job} object.
\begin{description}
-\item [set_events] The set_events takes a single
+\item [set\_events] The set\_events takes a single
argument, which is the instantation of the Job Events class
that contains the methods that you want called. The method
names that will be called must correspond to the Bacula
Bacula TLS (Transport Layer Security) is built-in network
encryption code to provide secure network transport similar to
-that offered by {\bf stunnel} or {\bs ssh}. The Bacula code was
+that offered by {\bf stunnel} or {\bf ssh}. The Bacula code was
written by Landon Fuller.
Supported features of this code include:
openssl dhparam -out dh1024.pem -5 1024
\end{verbatim}
-\end{itemize}
+\end{description}
\subsection*{Creating a Self-signed Certificate}
\index[general]{Creating a Self-signed Certificate }
projects / bacula / docs / commitdiff