> If you point me to the exact file where there are
> problems (the first
> occurrence), I will be happy to fix it.
here's the diff -Naur for docs/manual/tips.tex taken
from your CVS (less than 1h ago).
i removed all {\bf inside verbatim sections, and
corrected 1 typo NFS,NSF.
if i have time, i could clean up the rest. (lynx
*.html |grep "{\bf" ...)
=========
--- tips.tex 2006-09-29 18:10:16.000000000 +0000
+++ tips.tex.orig 2006-09-29 17:28:57.000000000
+0000
@@ -302,7 +302,7 @@
Note, one disadvantage of writing to an NFS mounted
volume as I do is
that if the other machine goes down, the OS will wait
forever on the fopen()
call that Bacula makes. As a consequence, Bacula will
completely stall until
-the machine exporting the NFS mounts comes back up. A
possible solution to this
+the machine exporting the NSF mounts comes back up. A
possible solution to this
problem was provided by Andrew Hilborne, and consists
of using the {\bf soft}
option instead of the {\bf hard} option when mounting
the NFS volume, which is
typically done in {\bf /etc/fstab}/. The NFS
documentation explains these
@@ -325,7 +325,7 @@
\footnotesize
\begin{verbatim}
(in the Console program)
-*restore
+*{\bf restore}
First you select one or more JobIds that contain
files
to be restored. You will then be presented several
methods
of specifying the JobIds. Then you will be allowed to
@@ -337,12 +337,12 @@
4: Enter SQL list command
5: Select the most recent backup for a client
6: Cancel
-Select item: (1-6): 5
+Select item: (1-6): {\bf 5}
The defined Client resources are:
1: Minimatou
2: Rufus
3: Timmy
-Select Client (File daemon) resource (1-3): 2
+Select Client (File daemon) resource (1-3): {\bf 2}
The defined FileSet resources are:
1: Kerns Files
Item 1 selected automatically.
@@ -360,7 +360,7 @@
remove files to be restored. All files are initially
added.
Enter "done" to leave this mode.
cwd is: /
-$ done
+$ {\bf done}
84 files selected to restore.
Run Restore job
JobName: kernsrestore
@@ -370,10 +370,10 @@
Client: Rufus
Storage: File
JobId: *None*
-OK to run? (yes/mod/no): no
-quit
+OK to run? (yes/mod/no): {\bf no}
+{\bf quit}
(in a shell window)
-cp ../working/restore.bsr
/mnt/deuter/files/backup/rufus.bsr
+{\bf cp ../working/restore.bsr
/mnt/deuter/files/backup/rufus.bsr}
\end{verbatim}
\normalsize
@@ -452,12 +452,12 @@
\footnotesize
\begin{verbatim}
-update
+{\bf update}
Update choice:
1: Volume parameters
2: Pool from resource
3: Slots from autochanger
-Choose catalog item to update (1-3): 1
+Choose catalog item to update (1-3): {\bf 1}
Defined Pools:
1: Default
2: File
@@ -467,7 +467,7 @@
+-------+---------+--------+---------+-----------+------+----------+------+-----+
| 1 | test01 | DDS-4 | Error | 352427156 |
... | 31536000 | 1 | 0 |
+-------+---------+--------+---------+-----------+------+----------+------+-----+
-Enter MediaId or Volume name: 1
+Enter MediaId or Volume name: {\bf 1}
\end{verbatim}
\normalsize
@@ -491,11 +491,11 @@
9: Volume Files
10: Pool
11: Done
-Select parameter to modify (1-11): 9
+Select parameter to modify (1-11): {\bf 9}
Warning changing Volume Files can result
in loss of data on your Volume
Current Volume Files is: 10
-Enter new number of Files for Volume: 11
+Enter new number of Files for Volume: {\bf 11}
New Volume Files is: 11
Updating Volume "test01"
Parameters to modify:
@@ -510,7 +510,7 @@
9: Volume Files
10: Pool
11: Done
-Select parameter to modify (1-10): 1
+Select parameter to modify (1-10): {\bf 1}
\end{verbatim}
\normalsize
@@ -528,7 +528,7 @@
4: Full
5: Used
6: Read-Only
-Choose new Volume Status (1-6): 1
+Choose new Volume Status (1-6): {\bf 1}
New Volume status is: Append
Updating Volume "test01"
Parameters to modify:
@@ -543,7 +543,7 @@
9: Volume Files
10: Pool
11: Done
-Select parameter to modify (1-11): 11
+Select parameter to modify (1-11): {\bf 11}
Selection done.
\end{verbatim}
\normalsize
@@ -721,7 +721,7 @@
\footnotesize
\begin{verbatim}
-list volumes
+{\bf list volumes}
Using default Catalog name=BackupDB DB=bacula
Pool: Default
=========
> Yes, this is quite possible (Bacula changed). The
> manual is so big that I
> cannot possibly check the whole thing each time. If
> you give the the exact
> file where the problem exists, I can fix it.
i'm using 1.36.3 on sarge, so my session itself could
be outdated. so i didn't want to change the diff...
here it is (starting docs/manual/tips.tex:482)
=========
Parameters to modify:
1: Volume Status
2: Volume Retention Period
3: Volume Use Duration
4: Maximum Volume Jobs
5: Maximum Volume Files
6: Maximum Volume Bytes
7: Recycle Flag
8: Slot
9: InChanger Flag
10: Volume Files
11: Pool
12: Volume from Pool
13: All Volumes from Pool
14: Done
Select parameter to modify (1-14): 10
Warning changing Volume Files can result
in loss of data on your Volume
=========
mlistus
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
