WebJul 14, 2008 · It's because you have lots of .trc files and the shell is expanding that "*.trc" to a list that's longer than find can handle. You probably want something like this: WebApr 3, 2012 · How do overcome shell command line length? You have following option to get around these limitations: Use find or xargs command Use shell for / while loop find command example to get rid of “argument list too long” error $ find /nas/data/accounting/ -type f -exec ls -l {} \; $ find /nas/data/accounting/ -type f -exec /bin/rm -f {} \;
Logging Apache Flink
WebJun 23, 2024 · A typical way to handle the “argument list too long” error is via the find command: find -maxdepth 1 -mindepth 1 -type f -name "*.jpg" -delete Share Improve this answer Follow edited Jun 30, 2024 at 19:37 answered Jun 23, 2024 at 0:10 Sergiy Kolodyazhnyy 102k 19 269 479 This is a slow way to do what I already did, prior to … WebJul 6, 2006 · There is a limit in bash on how much memory the command line arguments can occupy. You might try using find and xargs instead. find ./ -iname "*.pdf" xargs -l 1000 zip -r -q -j abc.zip The xargs program will take the stdout from the " " pipe and use them for the command line arguments. fishguard newspapers
"-bash: /usr/bin/rename: Argument list too long" [duplicate]
WebYou cannot use a pattern for ls such as "ls *.txt" because you’ll get the arugment list too long error before the data can be piped through to xargs. In order to do pattern matching you have to use the find command. Using find to do the same move from source to target, you could do this: find source/ -name "*.txt" -exec mv {} target ; WebOct 4, 2024 · The arguments that are provided to the application's executable are too long to be processed. Solution: Shorten the argument list. Eliminate any redundant or … WebJul 1, 2012 · The reason this occurs is because bash actually expands the asterisk to every matching file, producing a very long command line. Try this: find . -name "*.pdf" -print0 … can a spider web catch a bullet