The reason it says "argument list too long" is because the argument list is too long. You're not going to solve this by cramming the arguments into find instead of rm -- its argument limit is no bigger than rm's! The solution to "too many arguments" is to not use too many arguments. Just give find the directory and it is capable of finding the files itself -- after all, it is "find".
Here's a safer solution with xargs instead of parallel:
Hai I just want to find a file *.txt in particular direcotry and display the file name puls the content. Do someone know hot to do this, thanks.
I try :
find test/ -name '*.txt' | xargs cat
but It does'nt print out the file name, i want something below print out in my screen :
test/1.txt... (4 Replies)
I'm using Imagemagick to create thumbnails for a large directory tree. The only thing I can't see is how to get it to write the thumbnails to a "thumbs" subdirectory!
Either of these two commands from the Imagemagick site does most of the job:
find -name '*.jpg' | xargs -n1 sh -c 'convert $0... (5 Replies)
Hi,
I am having trouble getting a combination of commands to work.
I need to traverse through all sub-directories of a certain directory and 'cat' the contents of a particular file in the sub-directories.
The commands on their own work but when I combine them I get no output.
The... (4 Replies)
I believe what is happening is rm is executing in the script on every directory and on failure of the first it stops although returns status 0.
find $HOME -name /directory/filename | xargs -l rm
This is the code I use but file remains. I am using sun solaris system which has way limited... (4 Replies)
hi,
i've been trying to figure this weird error but I cannot seem to know why. I am using below find command:
find . \( ! -name . -prune \) -type f -mtime +365 -print
The above code returns no file because no files are really more then 365 days old. However, when I use xargs, its... (9 Replies)
Guys i want to run a command to list all directories that havn't been modified in over 548 days ( 1.5 yrs ).
Id like to run a script to first print what the command finds ( so i get a list of the files pre move ... i have a script set for this :
find /Path/Of\ Target/Directory/ -type d -mtime... (4 Replies)
How can I recursively find all files in a directory and print out the file and first line number of any text blocks that match the below cases?
This would seem to involve find, xargs, *grep, regex, etc.
In summary, I want to find so-called empty "try-catch blocks" that do not contain code... (0 Replies)
Hi All,
i'm trying to create a tar of all the .txt files i find in my dir . I've used xargs to acheive this but i wanted to do this with exec and looks like it only archives the last file it finds . can some one advice what's wrong here :
find . -type f -name "*.txt" -print0 | xargs -0... (9 Replies)
Hi,
I want to find some files and then search for some lines in it with a particular pattern and then write those lines into a file. To do this I am using something like this from command prompt directly.
cd /mdat/BVG
find -name "stmt.*cl" -newer temp.txt | xargs -i awk '/BVG-/{print}' {} >... (7 Replies)
hello,
bash 4.2+
osx 10.11.6
i looking for a nice compact one-liner and need a little help using find and xargs
i'm writing a script to recursively search through directories looking for git and hg repos and update them.
this bit of code searches and finds them git repos.
find `pwd`... (2 Replies)
Discussion started by: f77hack
2 Replies
LEARN ABOUT NETBSD
pathchk
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