From: <gi...@ba...> - 2013-05-12 08:37:15
|
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Bacula Community manual". The branch, Branch-5.2 has been updated via 47a4b8fa1e53db98fb82955e9a8d9276859b9fe7 (commit) from 2a4cb4ab916d95723a246840969e65852f8df183 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 47a4b8fa1e53db98fb82955e9a8d9276859b9fe7 Author: Kern Sibbald <ke...@si...> Date: Sun May 12 10:35:45 2013 +0200 Tweak doc text Conflicts: docs/manuals/en/main/fileset.tex ----------------------------------------------------------------------- Summary of changes: diff --git a/docs/manuals/en/main/fileset.tex b/docs/manuals/en/main/fileset.tex index cd9df3c..7eea8e7 100644 --- a/docs/manuals/en/main/fileset.tex +++ b/docs/manuals/en/main/fileset.tex @@ -1274,7 +1274,7 @@ without any options, but all files in those directories with the extensions {\bf .o} and {\bf .exe} will be excluded. Let's say that you now want to exclude the directory /tmp. The simplest way -to do so is to add an exclude directive that lists /tmp. The example +to do so is to add an Exclude directive that lists /tmp. The example above would then become: \footnotesize @@ -1307,11 +1307,11 @@ FileSet { You can add wild-cards to the File directives listed in the Exclude -directory, but you need to take care because if you exclude a directory, +directive, but you need to take care because if you exclude a directory, it and all files and directories below it will also be excluded. -Now lets take a slight variation on the above and suppose -you want to save all your whole filesystem except {\bf /tmp}. +Now let's make a slight variation on the above and suppose +you want to save all your filesystems except {\bf /tmp}. The problem that comes up is that Bacula will not normally cross from one filesystem to another. Doing a {\bf df} command, you get the following output: hooks/post-receive -- Bacula Community manual |