One of the following values describing the returned .Vt FTSENT structure and the file it represents. With the exception of directories without errors (FTS_D), all of these entries are terminal, that is, they will not be revisited, nor will any of their descendants be visited.
A directory being visited in pre-order.
A directory that causes a cycle in the tree. (The fts_cycle field of the .Vt FTSENT structure will be filled in as well.)
Any .Vt FTSENT structure that represents a file type not explicitly described by one of the other fts_info values.
A directory which cannot be read. This is an error return, and the fts_errno field will be set to indicate what caused the error.
A file named . or .. which was not specified as a file name to fts_open (see FTS_SEEDOT).
A directory being visited in post-order. The contents of the .Vt FTSENT structure will be unchanged from when it was returned in pre-order, i.e., with the fts_info field set to FTS_D.
This is an error return, and the fts_errno field will be set to indicate what caused the error.
A regular file.
A file for which no stat(2) information was available. The contents of the fts_statp field are undefined. This is an error return, and the fts_errno field will be set to indicate what caused the error.
A file for which no stat(2) information was requested. The contents of the fts_statp field are undefined.
A symbolic link.
A symbolic link with a non-existent target. The contents of the fts_statp field reference the file characteristic information for the symbolic link itself.
A path for accessing the file from the current directory.
The path for the file relative to the root of the traversal. This path contains the path specified to fts_open as a prefix.
The length of the string referenced by fts_path.
The name of the file.
The length of the string referenced by fts_name.
The depth of the traversal, numbered from -1 to N, where this file was found. The .Vt FTSENT structure representing the parent of the starting point (or root) of the traversal is numbered FTS_ROOTPARENTLEVEL (-1), and the .Vt FTSENT structure for the root itself is numbered FTS_ROOTLEVEL (0).
Upon return of a .Vt FTSENT structure from the fts_children or fts_read functions, with its fts_info field set to FTS_DNR, FTS_ERR or FTS_NS, the fts_errno field contains the value of the external variable errno specifying the cause of the error. Otherwise, the contents of the fts_errno field are undefined.
This field is provided for the use of the application program and is not modified by the fts functions. It is initialized to 0. Note that this field is overlaid by fts_bignum.
This field is provided for the use of the application program and is not modified by the fts functions. It is initialized to NULL. Note that this field is overlaid by fts_bignum.
This field is provided for the use of the application program and is not modified by the fts functions. It is initialized to 0. Note that this field overlays fts_number and fts_pointer.
A pointer to the .Vt FTSENT structure referencing the file in the hierarchy immediately above the current file, i.e., the directory of which this file is a member. A parent structure for the initial entry point is provided as well, however, only the fts_level, fts_bignum, fts_number and fts_pointer fields are guaranteed to be initialized.
Upon return from the fts_children function, the fts_link field points to the next structure in the NULL-terminated linked list of directory members. Otherwise, the contents of the fts_link field are undefined.
If a directory causes a cycle in the hierarchy (see FTS_DC), either because of a hard link between two directories, or a symbolic link pointing to a directory, the fts_cycle field of the structure will point to the .Vt FTSENT structure in the hierarchy that references the same file as the current .Vt FTSENT structure. Otherwise, the contents of the fts_cycle field are undefined.
A pointer to stat(2) information for the file.
A single buffer is used for all of the paths of all of the files in the file hierarchy. Therefore, the fts_path and fts_accpath fields are guaranteed to be NUL -terminated only for the file most recently returned by fts_read. To use these fields to reference any files represented by other .Vt FTSENT structures will require that the path buffer be modified using the information contained in that .Vt FTSENT structures fts_pathlen field. Any such modifications should be undone before further calls to fts_read are attempted. The fts_name field is always NUL -terminated.
Note that the use of fts_bignum is mutually exclusive with the use of fts_number or fts_pointer.
This option causes any symbolic link specified as a root path to be followed immediately whether or not FTS_LOGICAL is also specified.
This option causes the fts routines to return .Vt FTSENT structures for the targets of symbolic links instead of the symbolic links themselves. If this option is set, the only symbolic links for which .Vt FTSENT structures are returned to the application are those referencing non-existent files. Either FTS_LOGICAL or FTS_PHYSICAL must be provided to the fts_open function.
As a performance optimization, the fts functions change directories as they walk the file hierarchy. This has the side-effect that an application cannot rely on being in any particular directory during the traversal. The FTS_NOCHDIR option turns off this optimization, and the fts functions will not change the current directory. Note that applications should not themselves change their current directory and try to access files unless FTS_NOCHDIR is specified and absolute pathnames were provided as arguments to fts_open.
By default, returned .Vt FTSENT structures reference file characteristic information (the statp field) for each file visited. This option relaxes that requirement as a performance optimization, allowing the fts functions to set the fts_info field to FTS_NSOK and leave the contents of the statp field undefined.
This option causes the fts routines to return .Vt FTSENT structures for symbolic links themselves instead of the target files they point to. If this option is set, .Vt FTSENT structures for all symbolic links in the hierarchy are returned to the application. Either FTS_LOGICAL or FTS_PHYSICAL must be provided to the fts_open function.
By default, unless they are specified as path arguments to fts_open, any files named . or .. encountered in the file hierarchy are ignored. This option causes the fts routines to return .Vt FTSENT structures for them.
This option prevents fts from descending into directories that have a different device number than the file from which the descent began.
The argument compar specifies a user-defined function which may be used to order the traversal of the hierarchy. It takes two pointers to pointers to .Vt FTSENT structures as arguments and should return a negative value, zero, or a positive value to indicate if the file referenced by its first argument comes before, in any order with respect to, or after, the file referenced by its second argument. The fts_accpath, fts_path and fts_pathlen fields of the .Vt FTSENT structures may never be used in this comparison. If the fts_info field is set to FTS_NS or FTS_NSOK, the fts_statp field may not either. If the compar argument is NULL, the directory traversal order is in the order listed in path_argv for the root paths, and in the order listed in the directory for everything else.
Re-visit the file; any file type may be re-visited. The next call to fts_read will return the referenced file. The fts_stat and fts_info fields of the structure will be reinitialized at that time, but no other fields will have been changed. This option is meaningful only for the most recently returned file from fts_read. Normal use is for post-order directory visits, where it causes the directory to be re-visited (in both pre and post-order) as well as all of its descendants.
The referenced file must be a symbolic link. If the referenced file is the one most recently returned by fts_read, the next call to fts_read returns the file with the fts_info and fts_statp fields reinitialized to reflect the target of the symbolic link instead of the symbolic link itself. If the file is one of those most recently returned by fts_children, the fts_info and fts_statp fields of the structure, when returned by fts_read, will reflect the target of the symbolic link instead of the symbolic link itself. In either case, if the target of the symbolic link does not exist the fields of the returned structure will be unchanged and the fts_info field will be set to FTS_SLNONE.
If the target of the link is a directory, the pre-order return, followed by the return of all of its descendants, followed by a post-order return, is done.
No descendants of this file are visited. The file may be one of those most recently returned by either fts_children or fts_read.