Q. While using mv or rm command I get command line length error (Argument list too long error). How do I find out current running shell command line length limitations? How do I overcomes these limitations while writing UNIX / BSD / Linux shell utilities?
A. All shell have / has a limit for the command line length. UNIX / Linux / BSD system has a limit on how many bytes can be used for the command line argument and environment variables. When you start a new process or type a command these limitations are applied and you will see an error message as follows on screen:
Argument list too long
How do I find out current command line length limitations?
Type the following command (works under Linux / UNIX / BSD operating systems):
$ getconf ARG_MAX
Sample output:
262144
BSD operating system also supports following command:
$ sysctl kern.argmax
Sample output:
kern.argmax=262144
To get accurate picture about limitation type the following command (hat tip to Jeff):
$ echo $(( $(getconf ARG_MAX) - $(env | wc -c) ))
Output:
261129
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 {} \;
xargs command example to get rid of "argument list too long" error
$ echo /nas/data/accounting/* | xargs ls -l
$ echo /nas/data/accounting/* | xargs /bin/rm -f
while loop example to get rid of "argument list too long" error
ls -1 /nas/data/accounting/ | while read file; do mv /nas/data/accounting/$file /local/disk/ ; done
Alternatively, you can combine above methods:
find /nas/data/accounting/ -type f |
while read file
do
mv /nas/data/accounting/$file /local/disk/
donetime command - give resource usage
Use time command to find out exact system resource usage for each command:
$ time find blah blah
$ time ls -1 blah | while read file; do #blah on $file; done
Further readings:- Your shell documentation
- man pages ksh, bash, getconf, sysconf, sysctl, find, and xargs
Featured Articles:
- 20 Linux System Monitoring Tools Every SysAdmin Should Know
- 20 Linux Server Hardening Security Tips
- My 10 UNIX Command Line Mistakes
- Linux: 20 Iptables Examples For New SysAdmins

- 25 PHP Security Best Practices For Sys Admins
- The Novice Guide To Buying A Linux Laptop
- 10 Greatest Open Source Software Of 2009
- Top 5 Email Client For Linux, Mac OS X, and Windows Users
- Top 20 OpenSSH Server Best Security Practices
- Top 10 Open Source Web-Based Project Management Software
- Top 5 Linux Video Editor Software
Share this with other sys admins!
Facebook it - Tweet it - Print it -

Facebook it - Tweet it - Print it -


{ 3 comments… read them below or add one }
When using ‘+’ as end for find(1), you emulate xargs behavior, in that it will only pass the arguments to the command when the argument list is saturated, getting rid of numerous forks.
Brief & precise, very helpful and just what I was looking for. Thanks.
It is a small world… I just googled something unrelated and found this page. Then I noticed that command and realized you linked my website. Thanks!