Commit Graph

11 Commits

Author SHA1 Message Date
jilles
c25bdaf47d 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
2010-05-01 22:10:45 +00:00
jilles
b1c9a3a821 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
2010-05-01 22:00:28 +00:00
ru
0491ba1f63 Sync program's usage() with manpage's SYNOPSIS. 2005-05-21 09:55:10 +00:00
ru
7f3c7f0d46 Sort sections. 2005-01-18 13:43:56 +00:00
ru
6cc4b6c220 Added the EXIT STATUS section where appropriate. 2005-01-17 07:44:44 +00:00
tjr
d1851c5aa8 Unbreak support for systems that have no limit on pathname length.
Noticed by:	bde
2002-12-15 00:40:47 +00:00
tjr
6f784b854c 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
2002-12-14 11:44:54 +00:00
ru
041d1287e8 Uniformly refer to a file system as "file system".
Approved by:	re
2002-12-12 17:26:04 +00:00
tjr
64fa162345 When stat(2) fails, put the name of the component it failed on in the
warning message as well as the path argument.
2002-06-10 10:03:46 +00:00
ru
b9e8cb66c9 mdoc(7) police: tidy up the markup. 2002-05-30 14:02:23 +00:00
tjr
6d08f800fd Add the pathchk utility, which checks pathnames for validity or
portability between POSIX systems.

Submitted by:	Chuck Rouillard (manpage, initial implementation)
2002-05-22 10:30:16 +00:00