The -c option on your tar command is causing a new file to be created with each invocation. When there are more files in your input file than can be placed on the command line xargs will invoke tar multiple times, and with each invocation tar creates a new file. What you are seeing in the final tar file is the set of files that were placed on the command line to tar with the last invocation.
To solve this problem, just remove the -c option:
Code:
xargs <$index tar -rf $archived_file
You also don't need to use cat; xargs can read from stdin so the index file can be redirected in making the process more efficient.
EDIT: One more thought...
Because the -r option always appends if the target file exists, you should always remove the file before executing your tar command:
Code:
rm -f $archived_file # ensure it doesn't exist
xargs <$index tar -rf $archived_file
Last edited by agama; 02-12-2012 at 11:21 AM..
Reason: additional thought
Hello.
Consider the following magic words:
# ls `which adduser`
ls: /usr/sbin/adduser: No such file or directory
#
Hmmm...
Then:
# ls /usr/sbin/adduser
/usr/sbin/adduser
#
Now what?
Unforunately this little sniippet is used in my debian woody server's mysql pre install script.... (2 Replies)
Hi,
I use the command
ls a\b\c\*.txt
from the command line on HP UNIX and it works fine - It lists all files matching *.txt in the a\b\c directory
When embeded in a ksh script
`ls a\b\c\*.txt`
it does not work - I get *.txt not found (even though there are files)
I tried... (10 Replies)
If I have a directory /directory1 and want to tar and zip everything in it into a file new_tar.tar.gz on disk (not tape)
How can I do it?
I tried tar -cv /new_tar.tar /directory1/*
But I got an error: tar: /dev/rmt/0: No such device or address (4 Replies)
Hello everyone!
I wrote a script for backing up a folder. It goes fine but today it started to spit out this error, when a folder is taring:
tar: 0511-194 Reached end-of-file before expected.
I didn't make any changes!
- OS: UNIX AIX ibm 3
- the folder I'm trying to tar is 11Gb large... (4 Replies)
Hi,
i have more than 300 tar files in directory and i want to zip all tar files to single file.
could anybody tell me the command since i know how to do zip for single tar file:
bash-3.00$gzip 2008_11_10.tar
bash-3.00$ pwd
/oracle1/archivebackup
in this directory i have lot files... (2 Replies)
I need to sort through a volume that contains video files by access time and delete files that have not been accessed over x days. I have to use the access time as video files are originals that do not get modified, just read
Testing commands on a local test folder...
$ date
Wed Sep 28... (10 Replies)
Hi. I am trying to start a script on my router that will execute even if i log off. To execute the script I write:
nohup ./dslconnection > dslstat.out 2>&1 &
It starts the job:
21968 admin 1604 S /bin/ash ./dslconnection
The problem is that when I log back in the job has been... (6 Replies)
Hi,
I have prepared a script and trying to execute it but not getting expected output. Could you please help and advise what is going wrong.
"If else" part in below script is not working basically.
I am running it on HP-UX.
for i in slpd puma sfmdb
do
echo "******\t$i\t*******"
echo... (10 Replies)
I ran into the following and still do not understand entirely the rationale behind this. If someone could explain why things are as they are I'd be thankful.
The following was tested on AIX 7.1 with ksh88, but i suspect that to be ubiquitous. In an installation routine i had to create a set of... (6 Replies)
Discussion started by: bakunin
6 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)