07-17-2006
I have found the same problem with tar showing too long arguments than I break up the command into two which are as follows :
find . -type f -name "*.bas" > include-file
tar -cvf newfile.tar -I include-file
this worked and my problem get sorted.
Cheers!
Prashant Singh.
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 Advanced & Expert Users
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
3. 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
4. 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
5. 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
6. 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
7. Solaris
Hi,
I wanted a script to find sum of files for a particular date, below is my script
ls -lrt *.req | nawk '$6 == "Aug"' | nawk '$7 == "1"'| awk '{sum = sum + $5} END {print sum}'
However, i get the error below
/usr/bin/ls: arg list too long
How do i fix that.
Many thanks before. (2 Replies)
Discussion started by: beginningDBA
2 Replies
8. 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
9. 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
10. UNIX for Beginners Questions & Answers
hi all
i am trying to tar and then zip files present dir by using the below command
tar -cvf ${abc}/xyz_backup_date_`date +%d%m%y%H%M%S`.tar xyz*
when the files are in less number the above command executes perfectly but when there are large number of files i am getting "arg list too... (5 Replies)
Discussion started by: manoj
5 Replies
LEARN ABOUT OSX
procsystime
procsystime(1m) USER COMMANDS procsystime(1m)
NAME
procsystime - analyse system call times. Uses DTrace.
SYNOPSIS
procsystime [-acehoT] [ -p PID | -n name | command ]
DESCRIPTION
procsystime prints details on system call times for processes, both the elapsed times and on-cpu times can be printed.
The elapsed times are interesting, to help identify syscalls that take some time to complete (during which the process may have slept). CPU
time helps us identify syscalls that are consuming CPU cycles to run.
Since this uses DTrace, only users with root privileges can run this command.
OPTIONS
-a print all data
-c print syscall counts
-e print elapsed times, ns
-o print CPU times, ns
-T print totals
-p PID examine this PID
-n name
examine processes which have this name
EXAMPLES
Print elapsed times for PID 1871,
# procsystime -p 1871
Print elapsed times for processes called "tar",
# procsystime -n tar
Print CPU times for "tar" processes,
# procsystime -on tar
Print syscall counts for "tar" processes,
# procsystime -cn tar
Print elapsed and CPU times for "tar" processes,
# procsystime -eon tar
print all details for "bash" processes,
# procsystime -aTn bash
run and print details for "df -h",
# procsystime df -h
FIELDS
SYSCALL
System call name
TIME (ns)
Total time, nanoseconds
COUNT Number of occurrences
DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver-
bose descriptions explaining the output.
EXIT
procsystime will sample until Ctrl-C is hit.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO
dtruss(1M), dtrace(1M), truss(1)
version 1.00 Sep 22, 2005 procsystime(1m)