Overview
pathchk checks a path name for problems: too long, containing a directory that cannot be searched, or, with -p, using characters outside the portable set. It is for scripts that create files on other systems and want to know whether the name will work there. It prints nothing and exits 0 when the name is fine.
Background
A pathchk utility appeared in FreeBSD 5.0, according to the macOS manual, which also says it conforms to POSIX.1-2001. Today the name covers GNU pathchk and the pathchk that macOS ships. The BusyBox 1.37.0 build used for this page has no pathchk applet. They agree on -p and -P.
Examples
Check that a name uses only portable characters; it succeeds silently:
pathchk -p good/name && echo ok
A name with a space is not in the portable character set, so the check fails:
pathchk -p 'a b' 2> /dev/null || echo not portable
Check an absolute path:
pathchk -p /usr/bin/x && echo ok
Options
-p
Check against the POSIX portable character set and length limits.
-P
Also reject empty names and names that start with a hyphen.
Common mistakes
Without -p, pathchk checks only against the limits of the current system, so a name can pass here and fail elsewhere. The portable set is letters, digits, dot, underscore and hyphen, with a limit of 14 characters per part in the strictest form, and some systems may allow less. pathchk does not check that the file exists.
Portability
This page has no BusyBox view: BusyBox has no pathchk applet. Only -p is in the Common examples. The Common examples were executed on GNU coreutils 9.11 and macOS system tools (see the development guide for the exact check).
About macOS pathchk
This is the pathchk in the system folders of macOS. It follows the BSD implementation.
References
Original explanations, with upstream documentation for further reading. FreeBSD references are comparison material, not a claim of Apple version equivalence.