PATHCHK(1) General Commands Manual PATHCHK(1)NAME
pathchk - check pathname
SYNOPSIS
pathchk [-p] path ...
OPTIONS -p Check against POSIX rules
EXAMPLES
pathchk /usr/src/file.c
# Check the accessibility of file.c
pathchk -p file # Check posix compliance of file
DESCRIPTION
Pathchk verifies path names and display error if paths are too long, contain names that are too long, go thru a non-searchable directory or
contain an invalid character in names. If the -p flag is specified, the POSIX rules apply instead of the rules of the current file system.
PATHCHK(1)
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 . -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
At the login prompt of a unix system I get no shell. The backup job ran without a new tape for three days, and when the user tries to logon the message "no shell" appears.
Is the system in the wrong directory for login? (19 Replies)
following situation...
- bourne shell script
- sb. should entry a path and the script should look if the path exists, when not it should restart the Input
...
echo "path\c"
read Inp
if ; then
echo " path doesn't exist, try again... "
(how to go back to the Inp?????)
else
echo "... (3 Replies)
Hi,
I want to set a cron job with the yesterday date in a unix server (solaris).
I tried TZ=CST+24 date +%Y%m%d but i had TZ=CST+24: not found
I tried `perl -mPOSIX -e 'print POSIX::strftime("%Y%m%d",localtime(time() - 86400)) '` it works but I'm not sure that all the clients have perl... (12 Replies)