History log of /freebsd-9.3-release/usr.bin/pathchk/
Revision Date Author Comments
267654 20-Jun-2014 gjb

Copy stable/9 to releng/9.3 as part of the 9.3-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation


225736 23-Sep-2011 kensmith

Copy head to stable/9 as part of 9.0-RELEASE release cycle.

Approved by: re (implicit)


207485 01-May-2010 jilles

pathchk(1): Fix the example so it allows arbitrary pathnames.

Spaces and various other characters in pathnames are not passed through
literally by xargs in its default mode. Instead, use find . -exec ... {} +

Although the -- argument is not strictly required here, add it anyway to
avoid surprises when modifying the code to find -f -somedir ...

MFC after: 1 week


207483 01-May-2010 jilles

pathchk: Add the new POSIX -P option.

This option checks for empty pathnames and components starting with '-'.
Our -p option also checks for the latter, which remains the case.

MFC after: 1 week


146466 21-May-2005 ru

Sync program's usage() with manpage's SYNOPSIS.


140420 18-Jan-2005 ru

Sort sections.


140368 17-Jan-2005 ru

Added the EXIT STATUS section where appropriate.


107888 15-Dec-2002 tjr

Unbreak support for systems that have no limit on pathname length.

Noticed by: bde


107856 14-Dec-2002 tjr

Update pathchk to reflect the fact that 1003.1-2001 now includes the
trailing null byte in PATH_MAX and _POSIX_PATH_MAX.

PR: 46035


107788 12-Dec-2002 ru

Uniformly refer to a file system as "file system".

Approved by: re


98093 10-Jun-2002 tjr

When stat(2) fails, put the name of the component it failed on in the
warning message as well as the path argument.


97602 30-May-2002 ru

mdoc(7) police: tidy up the markup.


97095 22-May-2002 tjr

Add the pathchk utility, which checks pathnames for validity or
portability between POSIX systems.

Submitted by: Chuck Rouillard (manpage, initial implementation)