Query: pathchk
OS: osx
Section: 1
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
PATHCHK(1) BSD General Commands Manual PATHCHK(1)NAMEpathchk -- check pathnamesSYNOPSISpathchk [-p] pathname ...DESCRIPTIONThe 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.EXAMPLESCheck whether the names of files in the current directory are portable to other POSIX systems: find . -print | xargs pathchk -pDIAGNOSTICSThe pathchk utility exits 0 on success, and >0 if an error occurs.SEE ALSOgetconf(1), pathconf(2), stat(2)STANDARDSThe pathchk utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').HISTORYA pathchk utility appeared in FreeBSD 5.0.BSDMay 21, 2002 BSD
Related Man Pages |
---|
pathchk(1p) - posix |
pathchk(1) - freebsd |
pathchk(1p) - centos |
pathchk(1) - hpux |
pathchk(1) - osf1 |
Similar Topics in the Unix Linux Community |
---|
Finding absolute pathnames longer than 100 characters |
complex find command |