PATHCHK(1) BSD General Commands Manual PATHCHK(1)NAME
pathchk -- check pathnames
SYNOPSIS
pathchk [-p] pathname ...
DESCRIPTION
The 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.
EXAMPLES
Check whether the names of files in the current directory are portable to other POSIX systems:
find . -exec pathchk -p {} +
or the more efficient:
find . -print0 | xargs -0 pathchk -p
SEE ALSO getconf(1), pathconf(2), stat(2)STANDARDS
The pathchk utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
A pathchk utility appeared in NetBSD 2.0.
BSD November 9, 2010 BSD
Check Out this Related Man Page
PATHCHK(1) BSD General Commands Manual PATHCHK(1)NAME
pathchk -- check pathnames
SYNOPSIS
pathchk [-p] pathname ...
DESCRIPTION
The 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.
EXAMPLES
Check whether the names of files in the current directory are portable to other POSIX systems:
find . -print | xargs pathchk -p
DIAGNOSTICS
The pathchk utility exits 0 on success, and >0 if an error occurs.
SEE ALSO getconf(1), pathconf(2), stat(2)STANDARDS
The pathchk utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
A pathchk utility appeared in FreeBSD 5.0.
BSD May 21, 2002 BSD
I need to modify my version of find in unix and get it to create and use two POSIX threads to carry out concurrent finding operations.
How do i get about doing this>?
If anyone could help me it would be much appreciated.
Thanx
Mariuca (1 Reply)
Hi,
I have tried both the options in small dummy scripts, but somehow i can't differentiate between the two.
find . -name H* -exec ls -l {} \;
find . -name H* | xargs ls -l
Both work the ditto way.
Any help is appreciated. (19 Replies)
Please help. This simple problem is really stumping me.
Is there are way to find absolute pathnames for all files on your system that are longer than 100 characters?
I'm using bash shell to attempt it, but have come up with nothing so far.
I appreciate any help offered.
Nauty (2 Replies)
Hi all,
I am trying to execute the following command:
find 'path' -ls -exec cksum {} \;
As you can see this simply finds files from a given path and runs cksum on them.
My problem is this, if i have a FIFO in a directory the find tries to execute cksum on it and gets stuck.
From the man page i... (9 Replies)