I highly appreciate any help, tips and tricks, and even if it's just a bug report I want to know that.
I'm also looking forward to documentation updates, and notifying me about mistakes will be politely answered, too.
|What to do in case of errors|
|First, please read the documentation to rule out the possibility that it's just a badly written sentence that caused misunderstanding. |
|The internal design|
|Entry data storage.|
|The basic data structure for entries; an entry can be a file, directory, or special node (symlink or device). |
|Debugging and error checking.|
|Depending on configure options (|
|A list of variables that can be set by commandline parameters or environment variables; these are used in nearly every action. |
|apr_hash_t *||ign___groups = NULL|
|All groups, addressed by name. |
|apr_hash_t* ign___groups = NULL|
All groups, addressed by name.
These kinds of ignore patterns are available:
./, just like a base-directory-relative path.
*as well as character classes
[a-z] have their usual meaning, and
**is a wildcard for directory levels.
You can use a backslash
\ outside of character classes to match usually special characters literally, eg.
\* within a pattern will match a literal asterisk character within a file or directory name. Within character classes all characters except
] are treated literally. If a literal
] should be included in a character class, it can be placed as the first character or also be escaped using a backslash.
/ as the base-directory
./[oa]pt ./sys ./proc/* ./home/**~
This would ignore files and directories called
opt in the root directory (and files below, in the case of a directory), the directory
/sys and everything below, the contents of
/proc (but take the directory itself, so that upon restore it gets created as a mountpoint), and all entries matching
*~ in and below
./syswill match only a file or directory named
sys. If you want to exclude a directories' files, but not the directory itself, use something like
./prefix the full path, starting with
/, is used.
/etc/**.dpkg-old /etc/**.dpkg-bak /**.bak /**~
The advantage of using full paths is that a later
load in another working copy (eg. when moving from versioning
/) does simply work; the patterns don't have to be modified.
Internally this simply tries to remove the working copy base directory at the start of the patterns; then they are processed as usually.
If a pattern does not match the wc base, and neither has the wild-wildcard prefix
/**, a warning is issued; this can be handled as usual.
man pcre(if the manpages are installed), and/or
perldoc perlre(if perldoc is installed)
These patterns have the form
PCRE in uppercase, to distinguish from modifiers).
This would match
/home/somebody and so on, but would not match
Note that the pathnames start with
./ , just like above, and that the patterns are anchored at the beginning. To additionally anchor at the end you could use a
$ at the end.
This takes advantage of the major and minor numbers of inodes (see
man 1 stat and
man 2 stat).
The rule is as follows:
This is because the mount-point (ie. the directory, where the other filesystem gets attached) should be versioned (as it's needed after restore), but all entries (and all binding mounts) should not.
The possible options
>= define a less-or-equal-than respective bigger-or-equal-than relationship, to ignore a set of device classes.
devpts, etc.; see
/proc/filesystems, the lines with
Mind NFS and smb-mounts, check if you're using md , lvm and/or device-mapper !
Note: The values are parsed with
strtoul() , so you can use decimal, hexadecimal (with
0x prepended) and octal (with
0 prepended) notation.
","as separators; not all combinations make sense.take.
sambato access files.
m:04:00; the following examples give only the numbers.
As an example: the file has mode
0750; a specification of
A real-world example:
0007:0000 would match all entries that have no right bits set for "others", and could be used to exclude private files (like
/etc/shadow). (Alternatively, the others-read bit could be used:
FSVS will give an error for invalid specifications, ie. ones that can never match; an example would be
For patterns with the
m (mode match) and
d (dironly) modifiers the filename pattern gets optional; so you don't have to give an all-match wildcard pattern (
./**) for these cases.
t,d,./var/vmail/** t./var/vmail/**/.*.sieve ./var/vmail/**
".*.sieve"files (or directories) below
/var/vmail, in all depths, and all directories there; but no other files.
If your files are at a certain depth, and you don't want all other directories taken, too, you can specify that exactly:
td./var/vmail/* td./var/vmail/*/* t./var/vmail/*/*/.*.sieve ./var/vmail/**
m:04:0 t,./etc/ ./**
/etc, but ignoring the files that are not world-readable (
Groups have to be considered as follows:
added manually, they should apply as usual
The easiest way seems to be to write the properties in the filesystem when the entries are allocated for being stored in the entry list, ie. at
commit time. The simplest way to do that would be in waa__output_tree() - we see that an entry is newly allocated, and push all (not already set) properties there. But that wouldn't work with the
prop-del command, as an automatically assigned property wouldn't get removed.
So there's the function ops__apply_group(), which is called in the appropriate places.
Referenced by ign___new_group().