*** UNIX MANUAL PAGE BROWSER ***

A Nergahak database for man pages research.

Navigation

Directory Browser

1Browse 4.4BSD4.4BSD
1Browse Digital UNIXDigital UNIX 4.0e
1Browse FreeBSDFreeBSD 14.3
1Browse MINIXMINIX 3.4.0rc6-d5e4fc0
1Browse NetBSDNetBSD 10.1
1Browse OpenBSDOpenBSD 7.7
1Browse UNIX v7Version 7 UNIX
1Browse UNIX v10Version 10 UNIX

Manual Page Search

Manual Page Result

0 Command: pathchk | Section: 1 | Source: Digital UNIX | File: pathchk.1.gz
pathchk(1) General Commands Manual pathchk(1) NAME pathchk - Checks path names SYNOPSIS pathchk [-p] pathname... STANDARDS Interfaces documented on this reference page conform to industry stan- dards as follows: pathchk: XPG4, XPG4-UNIX Refer to the standards(5) reference page for more information about in- dustry standards and associated tags. OPTIONS Performs path name checks based on POSIX portability standards. An er- ror message is sent if any of the following conditions are true: The byte length of the full path name is longer than allowed by POSIX stan- dards ({_POSIX_PATH_MAX}). The byte length of a component is longer than allowed by POSIX standards ({_POSIX_NAME_MAX}). A character in any component is not in the portable file name character set. OPERANDS The path name to be checked. DESCRIPTION The pathchk command checks that one or more path names are valid (that is, they can be used to access or create a file without causing syntax errors) and portable (that is, no file name truncation will result). By default, the pathchk command checks each component of each path name specified by the pathname argument based on the underlying file system. If the -p option is not specified, pathchk sends an error message if any of the following conditions are true: The byte length of the full path name is longer than allowed by the system ({PATH_MAX} bytes). The byte length of a component is longer than allowed by the system ({NAME_MAX} bytes). Search permission is not allowed for a component. A character in any component 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 argument could be created without violating any of the preced- ing criteria. EXAMPLES To check the validity and portability of the /u/bob/work/tempfiles path name, enter: pathchk /u/bob/work/tempfiles To check the validity and portability of the /u/bob/temp path name for POSIX standards, enter: pathchk -p /u/bob/temp ENVIRONMENT VARIABLES The following environment variables affect the execution of pathchk: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization variables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi- byte characters in arguments). Determines the locale for the format and contents of diagnostic messages written to standard error. Deter- mines the location of message catalogues for the processing of LC_MES- SAGES. FILES System maximum values EXIT STATUS The pathchk command returns the following exit values: All path name operands passed the checks. An error occurred. SEE ALSO Commands: test(1) Files: limits(4) Standards: standards(5) pathchk(1)

Navigation Options