Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Arg list too long
Top Forums UNIX for Dummies Questions & Answers Arg list too long Post 302764501 by Don Cragun on Thursday 31st of January 2013 02:45:24 PM
Old 01-31-2013
I assume that bipinajith's proposed solution will still fail because /app/folder1/* is expanding to a list of arguments too long to process. The following should avoid that problem and be MUCH more efficient:
Code:
find /app/folder1 -name '*.dat' -type f -exec grep '.sh' {} +

Note, however, that if your .dat files are binary files (rather than text files) grep might not work. (The standards only specify the behavior of grep when its input files are text files.)

Also note that if grep is called with only one file operand, the name of the file in which the line is found will not be printed; just the contents of the matching line. If your .dat files are text files and you want the name of the file to be printed as well as the matched lines even if there is only one file operand, add /dev/null as another file operand. If you only want the names of matching files, but don't need to see the matched lines use the -l (letter ell; not digit 1) option.

And note that the pattern specified by '.sh' is a basic regular expression will match the two characters sh as long as they are not the 1st two characters on a line. If you want to match the three characters .sh, you need to add the -F option, use the obsolescent fgrep utility instead of grep, or escape the period in the BRE.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

arg list too long

I do ls -l ABC*, I get arg list too long message. This will not happen if ABC* has small no of files I believe 4000 files is limit. Any way of avoiding this. I even tried like this for i in `ls -l ABC*` do echo $i done Same problem. Any solution would be great. I am on HP-UX... (5 Replies)
Discussion started by: vingupta
5 Replies

2. UNIX for Dummies Questions & Answers

egrep and Arg list too long

hi everyone, We have a heck of a lot of files in a particular directory and I need to search through all of them to find a list of all files containing particular text strings...one being a date and the other being the name of the report that is printed on the files..... I've tried the... (6 Replies)
Discussion started by: kingo
6 Replies

3. UNIX for Dummies Questions & Answers

zcat --> Arg list too long

Hi all I have more than 1000 files in a folder and when ever i use a "compress" or "zcat" command it give error /bin/zcat: Arg list too long. . any solution for this :o (3 Replies)
Discussion started by: muneebr
3 Replies

4. UNIX for Advanced & Expert Users

arg list too long

Does anyone have a solution for arg list too long error. I have got this from the web but I fail to make any sense out of it Thanks enc (8 Replies)
Discussion started by: encrypted
8 Replies

5. UNIX for Dummies Questions & Answers

ls -t arg list too long

echo dirname/filename* | xargs ls -t As a substitute doesn't give the results desired when I exceed the buffer size. I still want the files listed in chronological order, unfortunately xargs releases the names piecemeal...does anyone have any ideas? :( (4 Replies)
Discussion started by: CSU_Ram
4 Replies

6. UNIX for Dummies Questions & Answers

arg list too long when mv files?

hello all i need some help because i am a unix/linux dummy...i have the following: DIR1> has 121437 files in it with varying dates going back to early April, a sub dir DIR1/DIR2> has 55835 files in it I need to move all files (T*.*) out of DIR1 into DIR2 that are older than today? Ive been... (2 Replies)
Discussion started by: jamos007
2 Replies

7. UNIX for Dummies Questions & Answers

arg list too long when trying to tar files

Hi, I am trying to perform this task: tar -cvf tar.newfile ??????.bas I got error "arg list too long". Is ther any way around? I have about 1500 file need to be tar together. Thanks in advance (5 Replies)
Discussion started by: jds3
5 Replies

8. UNIX for Dummies Questions & Answers

Arg List too Long in SCP

Hey guys. I have a program written in which i am trying to get the files from one remote machine and transferring the files to another remote machine using SCP. It works fine for 50 or 60 files but when the files grows to 250 then i get an error message stating "Arg list too long". #scp -p... (5 Replies)
Discussion started by: chris1234
5 Replies

9. Shell Programming and Scripting

arg list too long

Hi, Help. I have a file that contains a list of users in a file. I want to cat the content of the file and feed it into sed to a preformated report. The error I got is "ksh: /usr/bin/sed: arg list too long" My method below. A=`cat FILE1.txt` B=`echo $A` sed "s#USERLIST#$B#" FILE2 >... (2 Replies)
Discussion started by: Zenwork
2 Replies

10. Shell Programming and Scripting

arg list too long error

Hello, I'm trying to search through 30,000 files in 1 directory, and am getting the "arg list too long" error. I've searched this forum and have been playing around with xargs and can't get that to work either. I'm using ksh on Solaris. Here's my original code: nawk "/Nov 21/{_=2}_&&_--"... (14 Replies)
Discussion started by: Kristin_in_CO
14 Replies

LEARN ABOUT CENTOS

trace-cmd

TRACE-CMD(1)															      TRACE-CMD(1)

NAME

       trace-cmd - interacts with Ftrace Linux kernel internal tracer

SYNOPSIS

       trace-cmd COMMAND [OPTIONS]

DESCRIPTION

       The trace-cmd(1) command interacts with the Ftrace tracer that is built inside the Linux kernel. It interfaces with the Ftrace specific
       files found in the debugfs file system under the tracing directory. A COMMAND must be specified to tell trace-cmd what to do.

COMMANDS

	   record  - record a live trace and write a trace.dat file to the
		     local disk or to the network.

	   report  - reads a trace.dat file and converts the binary data to a
		     ASCII text readable format.

	   hist    - show a histogram of the events.

	   options - list the plugin options that are available to *report*

	   start   - start the tracing without recording to a trace.dat file.

	   stop    - stop tracing (only disables recording, overhead of tracer
		     is still in effect)

	   extract - extract the data from the kernel buffer and create a trace.dat
		     file.

	   reset   - disables all tracing and gives back the system performance.
		     (clears all data from the kernel buffers)

	   split   - splits a trace.dat file into smaller files.

	   list    - list the available plugins or events that can be recorded.

	   listen  - open up a port to listen for remote tracing connections.

	   restore - restore the data files of a crashed run of trace-cmd record

	   stack   - run and display the stack tracer

	   check-events - parse format strings for all trace events and return
			  whether all formats are parseable

OPTIONS

       -h, --help
	   Display the help text.

       Other options see the man page for the corresponding command.

SEE ALSO

       trace-cmd-record(1), trace-cmd-report(1), trace-cmd-hist(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1),
       trace-cmd-reset(1), trace-cmd-restore(1), trace-cmd-stack(1), trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1), trace-cmd.dat(5),
       trace-cmd-check-events(1)

AUTHOR

       Written by Steven Rostedt, <rostedt@goodmis.org[1]>

RESOURCES

       git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git

COPYING

       Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).

NOTES

	1. rostedt@goodmis.org
	   mailto:rostedt@goodmis.org

								    06/11/2014							      TRACE-CMD(1)
All times are GMT -4. The time now is 04:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy