Sponsored Content
Full Discussion: zcat --> Arg list too long
Top Forums UNIX for Dummies Questions & Answers zcat --> Arg list too long Post 54596 by muneebr on Thursday 19th of August 2004 01:47:27 AM
Old 08-19-2004
ok the details are as follow :-

if the number of files in perticular directory are less thn 900 then the cat, zcat or compress commands are working fine.

but when the number is greater then 1000 and i use any of the above cmd it give me mentioned error.

is there any parameter tht can be changed ??

MB
 

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

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

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

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

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

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

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

NAME
compress, uncompress, zcat - Compresses and expands data SYNOPSIS
compress [-cCdfFnqvV] [-b bits] [file...] uncompress [-cCfFnqvV] [file...] zcat [-n] [file...] STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: compress: XCU5.0 uncompress: XCU5.0 zcat: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
Specifies the maximum number of bits to use to replace common substrings in the file. The default for bits is 16, with values of 9 through 16 acceptable. First, the algorithm uses 9-bit codes 257 through 512. Then it uses 10-bit codes, continuing until the bits limit is reached. (This option applies to the compress command only.) After the bits limit is attained, the compress command periodically checks the compression ratio. If it is increasing, compress continues to use the existing code dictionary. However, if the compression ratio decreases, compress discards the table of sub- strings and rebuilds it from the beginning. This lets the algorithm adapt to the next block of the file. [Tru64 UNIX] The -b option must be the last option on the command line. Makes compress and uncompress write to the standard out- put; no files are changed. The nondestructive behavior of zcat is identical to that of uncompress -c. [Tru64 UNIX] Produces out- put compatible with compress 2.0. [Tru64 UNIX] Uncompresses a file. When used with the compress command, forces the compression of file even if no reduction in the size of the file will occur. With both the compress and uncompress commands, if you run the command in the background and -f is not specified, you are prompted as to whether an existing file should be overwritten. [Tru64 UNIX] Specifies that no header has been added. [Tru64 UNIX] Speci- fies a quiet operation. This is the default. Diagnostics messages, which display if you specify the -v option, do not print. If the -q and -v options are both specified, the last one on the command line is honored. Prints the percentage reduction of each file when compressing the file. Prints messages to standard error concerning the expansion of each file when uncompressing the file. If the -q and -v options are both specified, the last one on the command line is honored. [Tru64 UNIX] Specifies a version. OPERANDS
The path name of a file to be processed. If - (hyphen) is used, standard input will be read. The compress command will create an output file name by appending a suffix of to the input file name. With the uncompress and zcat commands, if the file name has a suffix, the command will look for a file of that name. If the suffix is not specified, the command will append the suffix before searching for the file. The uncompress command will store output in a file named with the suffix removed if it was specified. If no suffix is specified, the uncompress command will accept file as the name of the output file and append a suffix before searching for the file. DESCRIPTION
The compress command reduces the size of the named files using adaptive Lempel-Ziv coding. Whenever possible, each file is replaced by one with the extension while keeping the same ownership modes, access, and modification times. If no files are specified, standard input is compressed to the standard output. Compressed files can be restored to their original form by using the uncompress or zcat command. The uncompress command replaces the compressed file with an uncompressed version of the file, identical to the file that was originally compressed with compress; the suffix is removed. When issuing an uncompress command, you can refer to the compressed target file with or without the suffix. If you do not specify the suffix, uncompress assumes it. The zcat command writes the uncompressed version of a compressed file to standard output. The compressed (.Z) files remain intact. The zcat command is identical to uncompress -c. When issuing a zcat command, you can refer to the compressed target file with or without the suffix; if you do not specify the suffix, zcat assumes it. [Tru64 UNIX] The compress command uses the modified Lempel-Ziv algorithm popularized in "A Technique for High Performance Data Compres- sion," Terry A. Welch, IEEE Computer, vol. 17, no. 6 (June 1984), pp. 8-19. The amount of compression obtained depends on the size of the input, the number of bits per code, and the distribution of common sub- strings. Typically, files containing source code or plain text are reduced by 50 to 60 percent. Compression is generally much better than that achieved by Huffman coding (as used in the pack command) or adaptive Huffman coding, and takes less time to compute. NOTES
[Tru64 UNIX] The compress command may not preserve the extended file attributes (property list) of a file, including the access control list (ACL) if any. Verify that any ACLs have not been removed or modified after using compress or uncompress. EXIT STATUS
The following exit values are returned: compress command Successful completion. An error occurred. One or more files were not compressed because they became larger. An error occurred. uncompress and zcat commands Successful completion. An error occurred. DIAGNOSTICS
Invalid arguments were specified on the command line. maxbits must follow -b. The file cannot be uncompressed because it was never com- pressed. The file was compressed by a program that could deal with more bits than the compress code on this machine. Recompress the file with smaller bits. file is assumed to be already compressed. Rename the file and try again. Respond y, or the locale's equivalent of a y, if you want the output file to be replaced; n, or the locale's equivalent of a n, if not. (The LC_MESSAGES variable determines the locale's equivalent of y or n.) A SIGSEGV violation was detected, which usually means that the input file is corrupted. Percentage of the input saved by compression (relevant only for -v). When the input file is not a regular file, (for example, a directory), it is left unal- tered. The input file has links; it is left unchanged. (See the ln command for more information.) No saving is achieved by compression. The input remains unchanged. EXAMPLES
To compress folder and print the savings, enter: compress -v folder The system responds with a message like: folder: Compression: 43.94% -- replaced with folder.Z The following command displays the uncompressed version of the testlog.Z file: zcat testlog.Z ENVIRONMENT VARIABLES
The following environment variables affect the execution of compress, uncompress, and zcat: Provides a default value for the international- ization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization variables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. SEE ALSO
Commands: pack(1), pcat(1), unpack(1) Files: acl(4) Standards: standards(5) compress(1)
All times are GMT -4. The time now is 05:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy