Updates

diff --git a/docs/developers/version.tex b/docs/developers/version.tex
index 2839c70a5fd7f12615d1032823753b73a1147df0..4033cf4e8ba8d3bcd62ae32fa7db5f66088643ee 100644 (file)
--- a/docs/developers/version.tex
+++ b/docs/developers/version.tex
@@ -1 +1 @@
-1.38.6-beta6 (16 March 2006)
+1.38.6 (28 March 2006)

diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex
index 2839c70a5fd7f12615d1032823753b73a1147df0..4033cf4e8ba8d3bcd62ae32fa7db5f66088643ee 100644 (file)
--- a/docs/manual-de/version.tex
+++ b/docs/manual-de/version.tex
@@ -1 +1 @@
-1.38.6-beta6 (16 March 2006)
+1.38.6 (28 March 2006)

diff --git a/docs/manual/console.tex b/docs/manual/console.tex
index 7c331d6dfb078823fd0daed9a98d8bf064a8e0cb..2c98c45f01a95c3e082bece6da9c1464cf7c5206 100644 (file)
--- a/docs/manual/console.tex
+++ b/docs/manual/console.tex
@@ -121,9 +121,74 @@ the case of nested prompts). In a few places such as where it is asking for a
 Volume name, the period will be taken to be the Volume name. In that case, you
 will most likely be able to cancel at the next prompt. 
 
-There are three keywords used to refer to Jobs that must be clearly
-understood. They are the following:
+\label{keywords}
+\subsection*{Alphabetic List of Console Keywords}
+\index[general]{Keywords!Alphabetic List of Console }
+\index[general]{Alphabetic List of Console Keywords }
+\index[console]{Keywords!Alphabetic List of Console }
+\index[console]{Alphabetic List of Console Keywords }
+\addcontentsline{toc}{subsection}{Alphabetic List of Console Keywords}
+Unless otherwise specified, each of the following keywords
+takes an argument, which is specified after the keyword following
+an equal sign. For example:
+
+\begin{verbatim}
+jobid=536
+\end{verbatim}
+
+Please note, this list is incomplete as it is currently in
+the process of being created and is not currently totally in 
+alphabetic
+order ...
+
 \begin{description}
+\item [restart]
+  Permitted on the python command, and causes the Python 
+  interpreter to be restarted. Takes no argument.
+\item [all]
+  Permitted on the status and show commands to specify all components or
+  resources respectively.
+\item [before]
+  Used in the restore command.
+\item [bootstrap]
+  Used in the restore command.
+\item [catalog]
+  Allowed in the use command to specify the catalog name
+  to be used.
+\item [catalogs]
+  Used in the show command. Takes no arguments.
+\item [client | fd]
+\item [clients]
+  Used in the show, list, and llist commands. Takes no arguments.
+\item [counters]
+  Used in the show command. Takes no arguments.
+\item [current]
+  Used in the restore command. Takes no argument.
+\item [days]
+\item [devices]
+  Used in the show command. Takes no arguments.
+\item [dir | director]
+\item [directors]
+  Used in the show command. Takes no arguments.
+\item [directory]
+  Used in the restore command.
+\item [done]
+  Used in the restore command. Takes no argument.
+\item [file]
+  Used in the restore command.
+\item [files]
+  Used in the list and llist commands. Takes no arguments.
+\item [fileset]
+\item [filesets]
+  Used in the show command. Takes no arguments.
+\item [help]
+  Used in the show command. Takes no arguments.
+\item [jobs]
+  Used in the show, list and llist commands. Takes no arguments.
+\item [jobmedia]
+  Used in the list and llist commands. Takes no arguments.
+\item [jobtotals]
+  Used in the list and llist commands. Takes no arguments.
 \item [jobid]
   The JobId is the numeric jobid that is printed in the Job
   Report output. It is the index of the database record for the
@@ -131,17 +196,48 @@ understood. They are the following:
   in the catalog database, the same JobId can be reused once a
   Job is removed from the catalog. Probably you will refer
   specific Jobs that ran using their numeric JobId.
+\item [job | jobname]
+  The Job or Jobname keyword refers to the name you specified
+  in the Job resource, and hence it refers to any number of
+  Jobs that ran.  It is typically useful if you want to list
+  all jobs of a particular name.
+\item [level]
+\item [listing]
+  Permitted on the estimate command. Takes no argument.
+\item [limit]
+\item [messages]
+  Used in the show command. Takes no arguments.
+\item [media]
+  Used in the list and llist commands. Takes no arguments.
+\item [nextvol | nextvolume]
+  Used in the list and llist commands. Takes no arguments.
+\item [on]
+  Takes no keyword.
+\item [off]
+  Takes no keyword.
+\item [pool]
+\item [pools]
+  Used in the show, list, and llist commands. Takes no arguments.
+\item [select]
+  Used in the restore command. Takes no argument.
+\item [storages]
+  Used in the show command. Takes no arguments.
+\item [schedules]
+  Used in the show command. Takes no arguments.
+\item [sd | store | storage]
 \item [ujobid]
   The ujobid is a unique job identification that is printed
   in the Job Report output. At the current time, it consists
   of the Job name (from the Name directive for the job) appended
   with the date and time the job was run. This keyword is useful
   if you want to completely identify the Job instance run.
-\item [job | jobname]
-  The Job or Jobname keyword refers to the name you specified
-  in the Job resource, and hence it refers to any number of
-  Jobs that ran.  It is typically useful if you want to list
-  all jobs of a particular name.
+\item [volume]
+\item [volumes]
+  Used in the list and llist commands. Takes no arguments.
+\item [where]
+  Used in the restore command.
+\item [yes]
+  Used in the restore command. Takes no argument.
 \end{description}
 
 \label{list}
@@ -257,6 +353,24 @@ delete Job JobId=n,m,o-r,t ...
    number. That is a "delete jobid" accepts lists and ranges of
    jobids.
 
+\item [disable job\lt{}job-name\gt{}]
+  \index[console]{enable}
+  This command permits you to disable a Job for automatic scheduling. 
+  The job may have been previously enabled with the Job resource      
+  {\bf Enabled} directive or using the console {\bf enable} command.
+  The next time the Director is restarted or the conf file is reloaded,
+  the Enable/Disable state will be set to the value in the Job resource
+  (default enabled).
+
+\item [enable job\lt{}job-name\gt{}]
+  \index[console]{enable}
+  This command permits you to enable a Job for automatic scheduling. 
+  The job may have been previously disabled with the Job resource      
+  {\bf Enabled} directive or using the console {\bf disable} command.
+  The next time the Director is restarted or the conf file is reloaded,
+  the Enable/Disable state will be set to the value in the Job resource
+  (default enabled).
+
 \label{estimate}
 \item [estimate]
    \index[console]{estimate}
@@ -892,6 +1006,85 @@ status [all | dir=\lt{}dir-name\gt{} | director |
    occurrence of each run statement for the job will be displayed for the
    period specified.
 
+   If your job seems to be blocked, you can get a general idea of the
+   problem by doing a {\bf status dir}, but you can most often get a 
+   much more specific indication of the problem by doing a
+   {\bf status storage=xxx}.  For example, on an idle test system, when
+   I do {\bf status storage=File}, I get:
+\footnotesize
+\begin{verbatim}
+status storage=File
+Connecting to Storage daemon File at 192.168.68.112:8103
+
+rufus-sd Version: 1.39.6 (24 March 2006) i686-pc-linux-gnu redhat (Stentz)
+Daemon started 26-Mar-06 11:06, 0 Jobs run since started.
+
+Running Jobs:
+No Jobs running.
+====
+
+Jobs waiting to reserve a drive:
+====
+
+Terminated Jobs:
+ JobId  Level   Files          Bytes Status   Finished        Name 
+======================================================================
+    59  Full        234      4,417,599 OK       15-Jan-06 11:54 kernsave
+====
+
+Device status:
+utochanger "DDS-4-changer" with devices:
+   "DDS-4" (/dev/nst0)
+Device "DDS-4" (/dev/nst0) is mounted with Volume="TestVolume002"
+Pool="*unknown*"
+    Slot 2 is loaded in drive 0.
+    Total Bytes Read=0 Blocks Read=0 Bytes/block=0
+    Positioned at File=0 Block=0
+Device "Dummy" is not open or does not exist.
+No DEVICE structure.
+
+Device "DVD-Writer" (/dev/hdc) is not open.
+Device "File" (/tmp) is not open.
+====
+
+In Use Volume status:
+====
+\end{verbatim}
+\normalsize
+
+Now, what this tells me is that no jobs are running and that none of
+the devices are in use.  Now, if I {\bf unmount} the autochanger, which
+will not be used in this example, and then start a Job that uses the
+File device, the job will block.  When I re-issue the status storage
+command, I get for the Device status:
+
+\footnotesize
+\begin{verbatim}
+status storage=File
+...
+Device status:
+Autochanger "DDS-4-changer" with devices:
+   "DDS-4" (/dev/nst0)
+Device "DDS-4" (/dev/nst0) is not open.
+    Device is BLOCKED. User unmounted.
+    Drive 0 is not loaded.
+Device "Dummy" is not open or does not exist.
+No DEVICE structure.
+
+Device "DVD-Writer" (/dev/hdc) is not open.
+Device "File" (/tmp) is not open.
+    Device is BLOCKED waiting for media.
+====
+...
+\end{verbatim}
+\normalsize
+
+Now, here it should be clear that if a job were running that wanted
+to use the Autochanger (with two devices), it would block because
+the user unmounted the device. The real problem for the Job I started
+using the "File" device is that the device is blocked waiting for
+media -- that is Bacula needs you to label a Volume.
+
 \item [unmount]
    \index[console]{unmount}
    This command causes the indicated Bacula Storage  daemon to unmount the

diff --git a/docs/manual/dirdconf.tex b/docs/manual/dirdconf.tex
index 30acd54bc6edeb1fe3f3002bbf8cb6086035d5db..5b2c9e87629aa23b43ad96fe489d21de30a9caf9 100644 (file)
--- a/docs/manual/dirdconf.tex
+++ b/docs/manual/dirdconf.tex
@@ -128,6 +128,11 @@ in the  graphical user interface. This directive is optional.
    Directory}  is done when the configuration file is read so that values such 
    as {\bf \$HOME} will be properly expanded. This directive is required.
 
+   If you have specified a Director user and/or a Director group on your
+   ./configure line with {\bf {-}{-}with-dir-user} and/or 
+   {\bf {-}{-}with-dir-group} the Working Directory owner and group will
+   be set to those values.
+
 \item [Pid Directory = \lt{}Directory\gt{}]
    \index[dir]{Pid Directory}
    \index[dir]{Directive!Pid Directory}
@@ -326,6 +331,12 @@ Clients, you must define a Job for each one.
    specify here followed by the date and time the  job was scheduled for
    execution. This directive is required. 
 
+\item [Enabled = \lt{}yes|no\gt{}]
+  \index[dir]{Enable}
+  \index[dir]Directive!Enable}
+  This directive allows you to enable or disable automatic execution
+  via the scheduler of a Job.
+
 \item [Type = \lt{}job-type\gt{}]
    \index[dir]{Type}
    \index[dir]{Directive!Type}

diff --git a/docs/manual/fileset.tex b/docs/manual/fileset.tex
index 8405a23ff09771b765cbe15e85f885274e9ffd9b..f93d8849f10a4863d42e9ef53290a3ebbda29598 100644 (file)
--- a/docs/manual/fileset.tex
+++ b/docs/manual/fileset.tex
@@ -666,7 +666,8 @@ Change: 2005-11-06 12:36:48.000000000 +0100
 
 {\bf \lt{}file-list\gt{}} is a list of directory and/or filename names
 specified with a {\bf File =} directive. To include names containing spaces,
-enclose the name between double-quotes. 
+enclose the name between double-quotes. Wild-cards are not interpreted
+in file-lists. They can only be specified in Options resources.
 
 There are a number of special cases when specifying directories and files in a
 {\bf file-list}. They are: 
@@ -899,6 +900,10 @@ Include {
    you must ensure that there is a reader program or Bacula will block, and
    after one minute, Bacula will time out the write to the fifo and move on
    to the next file.
+
+\item A file-list may not contain wild-cards. Use directives in the
+   Options resource if you wish to specify wild-cards or regular expression
+   matching.
 \end{itemize}
 
 \subsubsection*{FileSet Examples}

diff --git a/docs/manual/install.tex b/docs/manual/install.tex
index f2bd7b9c354377aedb0af946e3f4fafe2b93142c..3d6b8c715063aa958739a0c4d8849a74196e21db 100644 (file)
--- a/docs/manual/install.tex
+++ b/docs/manual/install.tex
@@ -840,10 +840,14 @@ customize your installation.
 
 \item [ {-}{-}with-dir-user=\lt{}User\gt{} ]
    \index[general]{{-}{-}with-dir-user }
-   This option allows you to specify the Userid used to  run the Director. The
-   Director must be started as root, but  doesn't need to run as root, and  after
-   doing preliminary initializations, it can "drop"  to the UserId specified on
-   this option. 
+   This option allows you to specify the Userid used to run the Director.  The
+   Director must be started as root, but doesn't need to run as root, and
+   after doing preliminary initializations, it can "drop" to the UserId
+   specified on this option.  
+   If you specify this option, you must
+   create the User prior to running {\bf make install}, because the
+   working directory owner will be set to {\bf User}.
+                       
 
 \item [ {-}{-}with-dir-group=\lt{}Group\gt{} ]
    \index[general]{{-}{-}with-dir-group }
@@ -851,6 +855,9 @@ customize your installation.
    Director must be started as root, but  doesn't need to run as root, and  after
    doing preliminary initializations, it can "drop"  to the GroupId specified
    on this option. 
+   If you specify this option, you must
+   create the Group prior to running {\bf make install}, because the
+   working directory group will be set to {\bf Group}.
 
 \item [ {-}{-}with-sd-user=\lt{}User\gt{} ]
    \index[general]{{-}{-}with-sd-user }

diff --git a/docs/manual/rpm-faq.tex b/docs/manual/rpm-faq.tex
index d95bb8123603ef1079cf39901ce35b29589774bf..e0b0e45ba14618928ff3e6cb317e49c14ac426dc 100644 (file)
--- a/docs/manual/rpm-faq.tex
+++ b/docs/manual/rpm-faq.tex
@@ -260,3 +260,34 @@ Sqlite support:
 
 \end{verbatim}
 \normalsize
+
+\subsection*{RPM Install Problems}
+\index[general]{RPM Install Problems}
+\addcontentsline{toc}{subsection}{RPM Install Options}
+In general the RPMs, once properly built should install correctly.
+However, when attempting to run the daemons, a number of problems
+can occur:
+\begin{itemize}
+\item [Wrong /var/bacula Permissions]
+  By default, the Director and Storage daemon do not run with
+  root permission. If the /var/bacula is owned by root, then it
+  is possible that the Director and the Storage daemon will not
+  be able to access this directory, which is used as the Working
+  Directory. To fix this, the easiest thing to do is:
+\begin{verbatim}
+  chown bacula:bacula /var/bacula
+\end{verbatim}
+\item [The Storage daemon cannot Access the Tape drive]
+  This can happen in some older RPM releases where the Storage
+  daemon ran under userid bacula, group bacula.  There are two
+  ways of fixing this: the best is to modify the /etc/init.d/bacula-sd
+  file so that it starts the Storage daemon with group "disk".
+  The second way to fix the problem is to change the permissions
+  of your tape drive (usually /dev/nst0) so that Bacula can access it.
+  You will probably need to change the permissions of the SCSI control
+  device as well, which is usually /dev/sg0.  The exact names depend
+  on your configuration, please see the Tape Testing chapter for
+  more information on devices.
+\end{itemize}
+ 
+

diff --git a/docs/manual/storedconf.tex b/docs/manual/storedconf.tex
index cc9007fe9f24145567937e149ca38d54691149f0..5f201da50c9e85dbd42a87c86bc3b46ec5b58a94 100644 (file)
--- a/docs/manual/storedconf.tex
+++ b/docs/manual/storedconf.tex
@@ -352,7 +352,7 @@ specified within the Device resource are specific to the Device.
   If the Device Type is not explicitly specified, then the mount point
   must exist when the Storage daemon starts.
 
-  This directive was implemented in Bacula version 1.39.5.
+  This directive was implemented in Bacula version 1.38.6.
 
 
 \item [Media Type = {\it name-string}]
@@ -903,7 +903,9 @@ default, Bacula will only write  one end of file to terminate the tape.
 \addcontentsline{toc}{subsection}{Devices that require a mount (DVD)}
 
 All the directives in this section are implemented only in
-Bacula version 1.37 and later.  As of version 1.39.5, the directives
+Bacula version 1.37 and later and hence are available in version 1.38.6.
+
+As of version 1.39.5, the directives
 "Requires Mount", "Mount Point", "Mount Command", and "Unmount Command"
 apply to removable filesystems such as USB in addition to DVD.
 

diff --git a/docs/manual/version.tex b/docs/manual/version.tex
index 2839c70a5fd7f12615d1032823753b73a1147df0..4033cf4e8ba8d3bcd62ae32fa7db5f66088643ee 100644 (file)
--- a/docs/manual/version.tex
+++ b/docs/manual/version.tex
@@ -1 +1 @@
-1.38.6-beta6 (16 March 2006)
+1.38.6 (28 March 2006)

diff --git a/docs/manual/win32.tex b/docs/manual/win32.tex
index 6d5ed2815c5c64a13a4a036bb6546675f44d22f6..64d078022bd183bc301dceaf79708d4a011f41c1 100644 (file)
--- a/docs/manual/win32.tex
+++ b/docs/manual/win32.tex
@@ -77,7 +77,7 @@ Finally, proceed with the installation.
 
 \item Next you will be asked to select an installation directory.  
 
-   \addcontentsline{lof}{figure}{Win32 Directory Selection Dialog}
+\addcontentsline{lof}{figure}{Win32 Directory Selection Dialog}
 \includegraphics{./win32-location.eps}  
 
 \item If you are installing for the first time, you will  be asked if you want