Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Arg list too long error while performing tar and zip operation Post 303031455 by stomp on Thursday 28th of February 2019 01:21:23 PM
Old 02-28-2019
Check your local tar man-page if tar supports to read file names from stdin.
Another option is cpio - a similar tool - which I'm quite sure it supports reading file names from stdin on your system too, even if i don't know the name and version yet.

If you tell us about specific versions information about your os and your tar command, somebody here may give more information.

Last edited by stomp; 02-28-2019 at 02:32 PM..
 

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 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. Shell Programming and Scripting

ls command - strange error - arg list too long

I am running a shell script which has the following command ls *.pdf | wc -l error: arg list too long Please post your thoughts on this.. (4 Replies)
Discussion started by: techmoris
4 Replies

9. 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

10. UNIX for Dummies Questions & Answers

Arg list too long

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
Z(1)							      General Commands Manual							      Z(1)

NAME
comprez - safely (un)tar and (de)feather files and directories SYNOPSIS
comprez [ -t | -T ] [ -v | -V ] [ -l | -L ] [ -gz | -z | -I | -lz | -Z | -zip | -jar ] [ -# ] [ -s suffix ] [ -m mode ] [ -p | -P ] [ -h ] [ -- ] file ... DESCRIPTION
Comprez is a simple, safe and convenient front-end for the compress(1), uncompress(1), gzip(1), bzip2(1), lzip(1), tar(1), zip(1) and unzip(1) utilities for compressing and uncompressing files and directories. It processes each of its arguments according to the type of the file or directory given: If the argument is a plain file, then the file is compressed, ie, feathered. If the argument is a compressed file with a name ending in .Z, .gz, .z, .bz2, .lz, .zip or .jar, then the file is uncompressed, ie, defeathered. If the argument is a directory, then the directory is archived into one tar or zip file which is then compressed, ie, tarred and feathered. If the argument is a compressed tar or zip archive with a name ending in .{tar.,tar,ta,t}{Z,gz,z,bz2,lz} or .{zip,jar}, then the archive is uncompressed and untarred, ie, untarred and defeathered. The new compressed or uncompressed version will be in the same directory as the original. A compressed file is always uncompressed into a file with the same name sans the feather suffix. A compressed tar or zip archive is always unpacked into a subdirectory with the same name as the archive sans the tar and feather suffix, even if the archive did not itself contain such a subdirectory. OPTIONS
-- Interprets all following arguments as files instead of options. -# Where # is a digit from 1 through 9. This option is passed on to gzip(1), bzip2(1), lzip(1) and zip(1) when feathering with them. --fast may be used instead of -1 and --best instead of -9. -gz Uses gzip(1) and a .gz compression suffix when feathering. -h Prints a helpful usage message. -I Uses bzip2(1) and a .bz2 compression suffix when feathering. -l Lists the file or directory name created resulting from each argument. -L Does not report created files or directories. Default. -lz Uses lzip(1) and a .lz compression suffix when feathering. -m mode Apply the given chmod(1) mode argument to any created tar and feather files. Before this argument is applied, the files have the same read and write permissions as the directories from which they were created. For security, the default argument is go-rwx. If the mode is -, then no argument is applied. See chmod(1) for all other allowable formats of this argument. -p Preserves modes when untarring by giving the p flag to tar(1). Default. -P Doesn't preserve modes when untarring by not giving the p flag to tar(1). This option may be necessary on systems where ordinary users are allowed to run chown(2). -s suffix Creates tar and feather files using the given suffix style. The default suffix style is .tar.Z. Note that the suffix style does not dictate the program used for feathering nor the compression suffix. -t Only lists the table of contents of the given files. Does not make any changes. -T (Un)tars and (de)feathers the given files according to their type. Default. -v Verbose output. For example, reports compression ratios when feathering. -V Non-verbose output. Does not report compression ratios. Default. -q is a synonym. -z Uses gzip(1) and a .z compression suffix when feathering. -Z Uses compress(1) and a .Z compression suffix when feathering. Default. -zip, -jar Uses zip(1) and a .zip or .jar compression suffix when tarring and/or feathering. The zip format combines tarring and feather- ing. WARNING: zip does not preserve complete Unix filesystem information for the files it archives, such as links, some permis- sions, etc. A tar(1)-based format should be used if this is required. ENVIRONMENT VARIABLES
ZOPTS This variable may be set to a string of the above options to supersede the default settings. They may still be overridden by options given on the command line. GZIP This environment variable for gzip(1) is not passed on by comprez so that gzip's behavior is standard and predictable. ZIPOPT, UNZIP These environment variables for zip(1) and unzip(1) are not passed on by comprez so that their behavior is standard and pre- dictable. BUGS
There should be an option to allow the use of another directory for temporary files needed during the (un)tarring and (de)feathering pro- cesses. This would make comprez more useful when the quota or disk is nearly full. There should be -k and -K options for keeping the original input files or not. CAVEATS
Comprez is written to work with gzip versions 1.2.3 and 1.2.4, bzip2 versions 0.9.0 and 1.0.0, Unix zip version 2.0.1 and Unix unzip ver- sion 5.12. Other versions will probably work safely, too, but should still be checked for compatibility. Every effort has been made to assure that the use of this program will not lead to the inappropriate deletion or corruption of any files. However, there are never any guarantees, so please use at your own risk. VERSION
2.6.1 AUTHOR
Steve Kinzler, kinzler@cs.indiana.edu, May 89/Jun 93/Aug 99/Dec 00 URL
http://www.cs.indiana.edu/~kinzler/z SEE ALSO
compress(1), uncompress(1), gzip(1), bzip2(1), lzip(1), tar(1), zip(1), unzip(1) 2.6.1 Z(1)
All times are GMT -4. The time now is 09:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy