<p>The bat is bconsole with extra communication capabilities and a set of
graphical user interfaces that utilize those capabilities. A bat programmer is
able to create interfaces interact with the director in all ways that a user
-can, by executing commands. When a command is entered by the interface, bat
+can, by executing commands. When a command is entered by an interface, bat
will type in the command in the console and will often times change the
-interface visible to the console so that the user can read the command as well
+visible interface to the console so that the user can read the command as well
as the resulting output from the director. Bat can also perform requests of the
daemon, that the user normally would not do. These would be the ability to
retrieve lists of various resources and also to perform requests of the director
-to query director daemon's sql server and the director will return the query
-results to bat.
+to query director daemon's sql server. The director will then forward the
+query results to bat.
</BODY>
</HTML>
drop downs and limiting widgets in the Job Plot window defaulting to the current
settings of the widgets in the Job List window.
-<p>There are many options in the context sensitive popup that appears when the user
+<p>There are many options in the context sensitive popup that appear when the user
right clicks on the job table.
<p>Listing console commands can be run to list the jobid, list the files on that jobid,
<p>An interface to view the logs that have been stored in the database for the jobid
can be viewed by using the show log for job option.
-If the database does not have a log, an interface explaining the modification that
+If the database does not have a log, an popup explaining the modification that
should be made to the bacula-dir.conf file will come up. The change is to add
catalog = all to the messages stanza of the messages resource that this job uses.
that will be filled in by default if the job is run manually.
<p>The context sensitive list that pops up when a job is right clicked will
-include a number of commands as well as 2 to open up other interfaces.
+include a number of commands as well as two to open up other interfaces.
<p>The user can run a list files command in the console that will display a
list of job id's that have been run and some associated data. This is similar
<p>The list nextvolume console command will tell the user the next volume that
will be asked for when this job is run. It will also show a list of past jobs.
+<p>There is a preferences item to determine whether a long list or a short list
+command will be run. It can be found from the menu by following settings -
+preferences then the miscellaneous tab.
+
<p>There are options to run commands to enable or disable the job as scheduled.
If disabled, the job will be re-enabled when the director daemon is restarted.
<br>
<font size=+1>
-<h3>The Two Restore Interfaces</h3>
+<h2>The Two Restore Interfaces</h2>
<p>Both restore interfaces accomplish the same 3 steps in different ways.
Those steps are to select jobs to restore from, give the user the
menu to start a restore. They are restore from time or restore from job.
<p>This interface is intended as a high performance restore option.
-It is a server side interaction to perform the steps by utilizing the
-text based restore capabilities of bacula. It interprets interactions with the
-server and displays a graphical front end for the user.
+It is a server side process. These interfaces assist in user in using the
+text based restore capabilities of the standard console. It interprets the text
+to display the information in a way that simplifies the restore procedure.
<p>The Opening interface will allow the user to choose selection criterion to
inform the server how to determine the set of backup job ids to use in the