Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pathchk(1) [freebsd man page]

PATHCHK(1)						    BSD General Commands Manual 						PATHCHK(1)

NAME
pathchk -- check pathnames SYNOPSIS
pathchk [-pP] pathname ... DESCRIPTION
The pathchk utility checks whether each of the specified pathname arguments is valid or portable. A diagnostic message is written for each argument that: o Is longer than PATH_MAX bytes. o Contains any component longer than NAME_MAX bytes. (The value of NAME_MAX depends on the underlying file system.) o Contains a directory component that is not searchable. It is not considered an error if a pathname argument contains a nonexistent component as long as a component by that name could be created. The options are as follows: -p Perform portability checks on the specified pathname arguments. Diagnostic messages will be written for each argument that: o Is longer than _POSIX_PATH_MAX (255) bytes. o Contains a component longer than _POSIX_NAME_MAX (14) bytes. o Contains any character not in the portable filename character set (that is, alphanumeric characters, '.', '-' and '_'). No com- ponent may start with the hyphen ('-') character. -P In addition to the default or -p checks, write a diagnostic for each argument that: o Is empty. o Contains a component that starts with a hyphen. EXIT STATUS
The pathchk utility exits 0 on success, and >0 if an error occurs. EXAMPLES
Check whether the names of files in the current directory are portable to other POSIX systems: find . -exec pathchk -p -- {} + SEE ALSO
getconf(1), pathconf(2), stat(2) STANDARDS
The pathchk utility conforms to IEEE Std 1003.1-2001 (``POSIX.1''). HISTORY
A pathchk utility appeared in FreeBSD 5.0. BSD
May 1, 2010 BSD

Check Out this Related Man Page

pathchk(1)						      General Commands Manual							pathchk(1)

NAME
pathchk - check path names SYNOPSIS
pathname... DESCRIPTION
The command checks that one or more path names are valid and portable. By default, the command checks each component of each path name specified by the pathname parameter based on the underlying file system. An error message is written for each path name operand that: o is longer than that allowed by the system. o contains any component longer than that allowed by the system. o contains any component in a directory that is not searchable. o contains any character in any component that is not valid in its containing directory. It is not considered an error if one or more components of a path name do not exist, as long as a file matching the path name specified by the pathname parameter could be created that does not violate any of the checks above. More extensive portability checks are performed when the flag is specified. Options The command supports the following option: Performs path name checks based on POSIX portability standards instead of the underlying file system. An error message is written for each path name that: o is longer than bytes. o contains any component longer than bytes. o contains any character in any component that is not in the portable file name character set. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified in the environment or is set to the empty string, the value of is used as a default for each unspecified or empty vari- able. If is not specified or is set to the empty string, a default of "C" (see lang(5)) is used instead of If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to "C". See environ(5). International Code Set Support Single-byte and multi-byte character code sets are supported. RETURN VALUE
Upon successful completion, returns zero; otherwise it returns nonzero to indicate an error. EXAMPLES
To check the validity and portability of the path name on your system, use: To check the validity and portability of the path name for POSIX standards, use: STANDARDS CONFORMANCE
pathchk(1)
Man Page