Manual Reference Pages - YAFIC.CONF (5)
yafic.conf -- yafic(1) configuration file
File Attribute Flags
Note About Order
Per-type Flag Masks
yafic.conf is the configuration file used by yafic(1). It specifies how yafic(1)
should examine the filesystem.
Blank lines are ignored.
You may use double quotes " to enclose strings with spaces. Escape double
quotes by prefixing them with a #146;.
Comments begin with #. Everything until the end of line is ignored.
You may escape # characters by either quoting them or prefixing them
with a #146;.
A line ending with #146; specifies that the line following it is to be
interpreted as its continuation.
Each line is of the form:
entry-name is the name of a file or directory (relative to the root. See the
-r option to yafic(1)) and
flags are which file attributes to check.
entry-name is a directory, its contents will also be checked using
flags. This behavior can be changed by using prefixes.
An entry defined with the form
will be ignored.
entry-name and its contents will not be examined. An entry defined like this:
will mean that the contents of
entry-name will not be looked at.
flags will apply to
entry-name and entry-name only. Finally, an entry defined like this:
will still have its contents checked. However,
flags will only apply to
entry-name. Its contents will keep their previous flags. If no flags were
previously defined, then the contents will inherit the flags from
entry-names parent. If there is no entry for
entry-names parent or the entry is an ignore entry, then the flags will be inherited from
entry-names grandparent, etc. This will continue up to the root until a non-ignored
entry is found. If none is found, the contents will inherit the default
Directories that serve as mount points for other filesystems are always
ignored and are never recursed into. To recurse into a mount point, an
entry for it must be explicitly defined.
FILE ATTRIBUTE FLAGS
Each entry can be checked for changes in certain file attributes.
These attributes are:
/another/file would have the flags
Number of links.
Creation timestamp/inode modification timestamp.
SHA-1 hash of contents.
flags is unspecified, it defaults to
pinugmch. Flags can be added or removed relative to the default
by prefixing them with + or -. For example:
The resultant flags for /some/file would be
For convenience, there are a few flag templates defined:
pinug. (Log file)
pinugsamch. (Ignore nothing)
Same as . (Ignore everything)
If a template is used, it must be the first listed. Flags may be
added or removed from a template by prefixing them with + or -
respectively. For example:
If you wish to know when files are added or removed from a directory, but
you dont care about changes to the directory or its contents, you must
use the E template rather than prefixing the directory with !.
NOTE ABOUT ORDER
Each entry is parsed in order. Entries defined later will override earlier
ones. So, for example:
means that /var and its contents will be ignored. However, /var/log and
its contents will be checked using the L template.
Changing the order changes the meaning:
In this case, /var and its contents are totally ignored. The /var/log
entry is overridden by the subsequent !/var.
PER-TYPE FLAG MASKS
Optionally, one or more of the following special entries can appear:
mask is parsed exactly like
flags, described previously.
When changes are detected in an entry, depending on the entrys type
(directory, file, symbolic links, special), one of the four masks
is checked. The change is reported only if the corresponding flag
is set in the mask.
By default, all masks have all flags
Note that when a mask for a particular type is set, only entries defined
afterwards inherit that mask.
Default yafic(1) configuration file.
|--> ||YAFIC.CONF (5) ||December 12, 2003 |
Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.