Updates

[bacula/docs] / docs / manual / tips.tex

diff --git a/docs/manual/tips.tex b/docs/manual/tips.tex
index 6c165016b8c93350b1eb4062735e1fbddf5b3da2..21d6b8328f38579994149a42bd3a54f048357dae 100644 (file)
--- a/docs/manual/tips.tex
+++ b/docs/manual/tips.tex
@@ -225,7 +225,7 @@ command:
 \end{verbatim}
 \normalsize
 
-which runs my ``watchdog'' script. As an example, I have added the Job codes
+which runs my "watchdog" script. As an example, I have added the Job codes
 \%c and \%d which will cause the Client name and the Director's name to be
 passed to the script. For example, if the Client's name is {\bf Watchdog} and
 the Director's name is {\bf main-dir} then referencing \$1 in the script would
@@ -623,7 +623,7 @@ run the job.
 \index[general]{Autochanger!Automatic Labeling Using Your }
 \addcontentsline{toc}{subsection}{Automatic Labeling Using Your Autochanger}
 
-If you have an autochanger but it does not support barcodes, using a ``trick''
+If you have an autochanger but it does not support barcodes, using a "trick"
 you can make Bacula automatically label all the volumes in your autochanger's
 magazine. 
 
@@ -784,8 +784,8 @@ Include.
 
 This tip also comes from Marc Brueckner. (Note, this tip is probably outdated
 by the addition of {\bf ClientRunBeforJob} and {\bf ClientRunAfterJob} Job
-records, but the technique still could be useful.) First I thought the ``Run
-Before Job'' statement in the Job-resource is for executing a script on the
+records, but the technique still could be useful.) First I thought the "Run
+Before Job" statement in the Job-resource is for executing a script on the
 remote machine(the machine to be backed up). It could be usefull to execute
 scripts on the remote machine e.g. for stopping databases or other services
 while doing the backup. (Of course I have to start the services again when the
@@ -827,7 +827,7 @@ ssh -i Bacula_key  -l root "ls -la"
 \end{verbatim}
 \normalsize
 
-This should execute the ``ls -la'' command on the remote machine. 
+This should execute the "ls -la" command on the remote machine. 
 
 Now you could add lines like the following to your Director's conf file: 
 
@@ -937,8 +937,8 @@ say thank you and let's bacula continue it's backup.
 So you can schedule and run backups without ever having to log on or see the
 console.
 To make the whole thing work you need to create a Device resource which looks
-something like this (``Archive Device'', ``Maximum Changer Wait'', ``Media
-Type'' and ``Label media'' may have different values): 
+something like this ("Archive Device", "Maximum Changer Wait", "Media
+Type" and "Label media" may have different values): 
 
 \footnotesize
 \begin{verbatim}
@@ -960,7 +960,7 @@ Device {
 \normalsize
 
 As the script has to emulate the complete wisdom of a mtx-changer it has an
-internal ``database'' containing where which tape is stored, you can see this on
+internal "database" containing where which tape is stored, you can see this on
 the following line:
 
 \footnotesize
@@ -971,8 +971,8 @@ VOL-0007 VOL-0008 VOL-0009 VOL-0010 VOL-0011 VOL-0012"
 \normalsize
 
 The above should be all on one line, and it effectivly tells Bacula that
-volume ``VOL-0001'' is located in slot 1 (which is our lowest slot), that
-volume ``VOL-0002'' is located in slot 2 and so on..
+volume "VOL-0001" is located in slot 1 (which is our lowest slot), that
+volume "VOL-0002" is located in slot 2 and so on..
 The script also maintains a logfile (/var/log/mtx.log) where you can monitor
 its operation.