History log of /freebsd-10.1-release/usr.bin/pathchk/pathchk.c
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
# 272461 02-Oct-2014 gjb

Copy stable/10@r272459 to releng/10.1 as part of
the 10.1-RELEASE process.

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

# 270890 31-Aug-2014 jilles

MFC r256800: pathchk: Ensure bytes >= 128 are considered non-portable
characters.

This was not broken on architectures such as ARM where char is unsigned.

Also, remove the first non-portable character from the output. POSIX does
not require this, and printing the first byte may yield an invalid byte
sequence with UTF-8.

PR: 165988
Reported by: Nicolas Rachinsky
Relnotes: yes


# 256281 10-Oct-2013 gjb

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

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


# 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.


# 107888 14-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


# 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.


# 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)