10-28-2004
I think the find syntax as you have it will have the same problem. If you use xargs like this you may have some luck. I am not anywhere I can test it right now to confirm for you but this syntax may work:
find ./ -print | xargs grep '^011.......$' *| cut -f1 -d :
If you run this from your top level directory where you were running your script, you should get the results you want.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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
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 Dummies Questions & Answers
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
5. UNIX for Dummies Questions & Answers
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
6. UNIX for Dummies Questions & Answers
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
7. UNIX for Dummies Questions & Answers
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
8. Shell Programming and Scripting
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
9. Shell Programming and Scripting
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
10. UNIX for Dummies Questions & Answers
Hello All,
I am trying to find a file name with .sh exention from a list of .dat files inside a directory.
find /app/folder1/* -name '*.dat'| xargs grep '.sh'
ksh: /usr/local/bin/find: arg list too long
Please help me finding the command.
Thanks (3 Replies)
Discussion started by: tkhan9
3 Replies
lndir(1X) lndir(1X)
NAME
lndir - create a shadow directory of symbolic links to another directory tree
SYNOPSIS
lndir fromdir [todir]
DESCRIPTION
lndir makes a shadow copy todir of a directory tree fromdir, except that the shadow is not populated with real files but instead with sym-
bolic links pointing at the real files in the fromdir directory tree. This is usually useful for maintaining source code for different
machine architectures. You create a shadow directory containing links to the real source which you will have usually NFS mounted from a
machine of a different architecture, and then recompile it. The object files will be in the shadow directory, while the source files in
the shadow directory are just symlinks to the real files.
This has the advantage that if you update the source, you need not propagate the change to the other architectures by hand, since all
source in shadow directories are symlinks to the real thing: just cd to the shadow directory and recompile.
The todir argument is optional and defaults to the current directory. The fromdir argument may be relative (e.g., ../src) and is relative
to todir (not the current directory).
Note that RCS, SCCS, and CVS.adm directories are not shadowed.
Note also that if you add files, you must run lndir again. Deleting files is difficult because the symlinks will point to places that no
longer exist.
BUGS
The patch routine needs to be able to change the files. You should never run patch from a shadow directory.
Use a command like the following to clear out all files before you can relink (if the fromdir has been moved, for instance):
find todir -type l -print | xargs rm
The following command will find all files that are not directories:
find . ! -type d -print
lndir(1X)