|Main index||Section 8||Options|
The options are as follows:
|Follow all symbolic links in the file hierarchy.|
|Do not follow symbolic links in the file hierarchy, instead consider the symbolic link itself in any comparisons. This is the default.|
|Modify the owner, group, permissions, and modification time of existing files to match the specification and create any missing directories or symbolic links. User, group and permissions must all be specified for missing directories to be created. Corrected mismatches are not considered errors.|
|Print a specification for the file hierarchy to the standard output.|
|Ignore everything except directory type files.|
|Do not complain about files that are in the file hierarchy, but not in the specification.|
Indent the output 4 spaces each time a directory level is descended when
creating a specification with the
Do not emit pathname comments when creating a specification.
a comment is emitted before each directory and before the close of that
directory when using the
|Quiet mode. Do not complain when a "missing" directory cannot be created because it already exists. This occurs when the directory is a symbolic link.|
|Remove any files in the file hierarchy that are not described in the specification.|
|Make some errors non-fatal warnings.|
|Do not descend below mount points in the file hierarchy.|
Read the specification from
instead of from the standard input.
If this option is specified twice, the two specifications are compared
to each other rather than to the file hierarchy.
The specifications will be sorted like output generated using
|Add the specified (whitespace or comma separated) keywords to the current set of keywords.|
|Use the ``type'' keyword plus the specified (whitespace or comma separated) keywords instead of the current set of keywords.|
|Use the file hierarchy rooted in path, instead of the current directory.|
|Display a single checksum to the standard error output that represents all of the files for which the keyword cksum was specified. The checksum is seeded with the specified value.|
|The specified file contains fnmatch(3) patterns matching files to be excluded from the specification, one to a line. If the pattern contains a ‘/’ character, it will be matched against entire pathnames (relative to the starting directory); otherwise, it will be matched against basenames only. No comments are allowed in the exclude-list file.|
Specifications are mostly composed of ``keywords'', i.e., strings that specify values relating to files. No keywords have default values, and if a keyword has no value set, no checks based on it are performed.
Currently supported keywords are as follows:
|cksum||The checksum of the file using the default algorithm specified by the cksum(1) utility.|
|flags||The file flags as a symbolic name. See chflags(1) for information on these names. If no flags are to be set the string "none" may be used to override the current default.|
|Ignore any file hierarchy below this file.|
|gid||The file group as a numeric value.|
|gname||The file group as a symbolic name.|
|The MD5 message digest of the file.|
|The FIPS 160-1 (" SHA-1") message digest of the file.|
|The FIPS 180-2 (" SHA-256") message digest of the file.|
|The RIPEMD160 message digest of the file.|
|mode||The current file's permissions as a numeric (octal) or symbolic value.|
|nlink||The number of hard links the file is expected to have.|
|Make sure this file or directory exists but otherwise ignore all attributes.|
|The file is optional; do not complain about the file if it is not in the file hierarchy.|
|uid||The file owner as a numeric value.|
|uname||The file owner as a symbolic name.|
|size||The size, in bytes, of the file.|
|link||The file the symbolic link is expected to reference.|
|time||The last modification time of the file, in seconds and nanoseconds. The value should include a period character and exactly nine digits after the period.|
The type of the file; may be set to any one of the following:
|block||block special device|
|char||character special device|
The default set of keywords are flags, gid, link, mode, nlink, size, time, and uid.
There are four types of lines in a specification.
The first type of line sets a global value for a keyword, and consists of the string ``/set'' followed by whitespace, followed by sets of keyword/value pairs, separated by whitespace. Keyword/value pairs consist of a keyword, followed by an equals sign (``=''), followed by a value, without whitespace characters. Once a keyword has been set, its value remains unchanged until either reset or unset.
The second type of line unsets keywords and consists of the string ``/unset'', followed by whitespace, followed by one or more keywords, separated by whitespace.
The third type of line is a file specification and consists of a file name, followed by whitespace, followed by zero or more whitespace separated keyword/value pairs. The file name may be preceded by whitespace characters. The file name may contain any of the standard file name matching characters (``['', ``]'', ``?'' or ``*''), in which case files in the hierarchy will be associated with the first pattern that they match.
Each of the keyword/value pairs consist of a keyword, followed by an equals sign (``=''), followed by the keyword's value, without whitespace characters. These values override, without changing, the global value of the corresponding keyword.
All paths are relative. Specifying a directory will cause subsequent files to be searched for in that directory hierarchy. Which brings us to the last type of line in a specification: a line containing only the string " .." causes the current directory path to ascend one level.
Empty lines and lines whose first non-whitespace character is a hash mark (``#'') are ignored.
utility exits with a status of 0 on success, 1 if any error occurred,
and 2 if the file hierarchy did not match the specification.
A status of 2 is converted to a status of 0 if the
|system specification directory|
To create an
style BSD.*.dist file, use
|MTREE (8)||June 16, 2007|
|Main index||Section 8||Options|
|“||"I liken starting one's computing career with Unix, say as an undergraduate, to being born in East Africa. It is intolerably hot, your body is covered with lice and flies, you are malnourished and you suffer from numerous curable diseases. But, as far as young East Africans can tell, this is simply the natural condition and they live within it. By the time they find out differently, it is too late. They already think that the writing of shell scripts is a natural act."||”|
|— Ken Pier, Xerox PARC|