Sponsored Content
Top Forums UNIX for Dummies Questions & Answers UNIX: 0403-027 The parameter list is too long Post 302326576 by otheus on Thursday 18th of June 2009 08:33:01 AM
Old 06-18-2009
If your command is something like this:
Code:
compress *

Replace it with
Code:
ls -1 |xargs compress

But if your command is something like one of
Code:
compress *.txt
compress 2009-*

Then you need to first use "find" (for the first example)
Code:

find . -name "*.txt" -print | xargs compress

 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Parameter List to Long

I am trying to do a find file command on a directory and delete files older then 30 days and I am getting an error saying that the parameter list that I am passing to the rm command is to long. Here is my command: find ~mydir/* -type f -mtime +$30 | xargs -i -exec rm -rf {} \; ksh:... (3 Replies)
Discussion started by: lesstjm
3 Replies

2. UNIX for Dummies Questions & Answers

Grep 0403-027 The parameter list is too long.

Hi there I get this error message when I try to do a basic grep. Does anyone have any ideas what is wrong. Thanks 0403-027 The parameter list is too long. (1 Reply)
Discussion started by: japada
1 Replies

3. HP-UX

parameter list too long

Hi When i say ls * (HP-UX 11.11)in a particular directory it says sh: /usr/bin/ls: The parameter list is too long. Can somebody help me how to resolve this problem. (2 Replies)
Discussion started by: satyanarayang
2 Replies

4. Shell Programming and Scripting

parameter list too long

This is one of shell things I guess. I have a directory in a production server that contains about 20,000 files. It gets cleaned up every week and is kept in check that it does not get out of hand. Here is my problem. When I perform a ls -ltr, I get the listing. However should I parameterize... (4 Replies)
Discussion started by: jerardfjay
4 Replies

5. UNIX for Dummies Questions & Answers

0403-027 The parameter list is too long.

hi when i ran the following command rm *_F i got this error 0403-027 The parameter list is too long. It shd remove 5000(around) files pls help me on this. why its throwing this error how to rectify this error (5 Replies)
Discussion started by: romiljain
5 Replies

6. Shell Programming and Scripting

Tar: Parameter list is too long

Hi all, I have a lot of files in my audit log directory which i am trying to tar. However, i hit the below error: ksh: /usr/bin/tar: 0403-027 The parameter list is too long. Is there any work around to resolve this problem? I need to tar all the files up. Thanks. (5 Replies)
Discussion started by: ahSher
5 Replies

7. Shell Programming and Scripting

/usr/bin/ls: 0403-027 the parameter list is too long.

Hi, I'm trying to list specific files and redirecting to a file ls aqp* > temp.lst but getting "/usr/bin/ls: 0403-027 the parameter list is too long." error. I just have 236 files in the directory. I tried "ls | grep 'aqp*' > temp.lst" too, but nothing was redirected. + grep aqp* +... (4 Replies)
Discussion started by: dateez
4 Replies

8. Shell Programming and Scripting

usr/bin/ls: 0403-027 The parameter list is too long

I ran this script in AIX 5L environment and getting an error usr/bin/ls: 0403-027 The parameter list is too long Our administrator had increased the maxium allowable size of the ARG/ENV list but it still doesn't work. I have tested the command in red below in the unix prompt and it works just... (13 Replies)
Discussion started by: hanie123
13 Replies

9. AIX

aix:ksh: /usr/bin/rm: 0403-027 The parameter list is too long.

Hi, I am getting the below error message When i am trying to delete the files from the directory.Could you please guide me? rm *.aud ksh: /usr/bin/rm: 0403-027 The parameter list is too long. and find /oracle/admin/testP/adump/*.aud -mtime +5 -exec rm {} \; ksh: /usr/bin/find:... (3 Replies)
Discussion started by: nokiae63
3 Replies

10. AIX

0403-027 The parameter list is too long on AIX 5.3

Hi we are using AIX 5.3 64bit I have near about 79000 log file having naming convention like "IFTMBCSun Aug 14 07:45:00 PAKST 2011". This naming convention was created by a script error, now we need to rename these log file by removing extar spaces and (:) colon for that we wrote below script ... (4 Replies)
Discussion started by: lodhi1978
4 Replies
COMPRESS(1)						    BSD General Commands Manual 					       COMPRESS(1)

NAME
compress, uncompress -- compress and expand data SYNOPSIS
compress [-cdfv] [-b bits] [file ...] uncompress [-cdfv] [file ...] DESCRIPTION
compress reduces the size of the named files using adaptive Lempel-Ziv coding. Each file is renamed to the same name plus the extension ``.Z''. As many of the modification time, access time, file flags, file mode, user ID, and group ID as allowed by permissions are retained in the new file. If compression would not reduce the size of a file, the file is ignored. uncompress restores the compressed files to their original form, renaming the files by deleting the ``.Z'' extension. If renaming the files would cause files to be overwritten and the standard input device is a terminal, the user is prompted (on the standard error output) for confirmation. If prompting is not possible or confirmation is not received, the files are not overwritten. If no files are specified, the standard input is compressed or uncompressed to the standard output. If either the input and output files are not regular files, the checks for reduction in size and file overwriting are not performed, the input file is not removed, and the attributes of the input file are not retained. The options are as follows: -b Specify the bits code limit (see below). -c Compressed or uncompressed output is written to the standard output. No files are modified. -d Force decompression. -f Force compression of file, even if it is not actually reduced in size. Additionally, files are overwritten without prompting for confirmation. -v Print the percentage reduction of each file. compress uses a modified Lempel-Ziv algorithm. Common substrings in the file are first replaced by 9-bit codes 257 and up. When code 512 is reached, the algorithm switches to 10-bit codes and continues to use more bits until the limit specified by the -b flag is reached (the default is 16). Bits must be between 9 and 16. After the bits limit is reached, compress 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 substrings and rebuilds it from scratch. This allows the algorithm to adapt to the next "block" of the file. The -b flag is omitted for uncompress since the bits parameter specified during compression is encoded within the output, along with a magic number to ensure that neither decompression of random data nor recompression of compressed data is attempted. The amount of compression obtained depends on the size of the input, the number of bits per code, and the distribution of common substrings. Typically, text such as source code or English is reduced by 50-60%. Compression is generally much better than that achieved by Huffman cod- ing (as used in the historical command pack), or adaptive Huffman coding (as used in the historical command compact), and takes less time to compute. The compress utility exits 0 on success, and >0 if an error occurs. SEE ALSO
zcat(1) Welch, Terry A., "A Technique for High Performance Data Compression", IEEE Computer, 17:6, pp. 8-19, June, 1984. HISTORY
The compress command appeared in 4.3BSD. BSD
January 23, 2003 BSD
All times are GMT -4. The time now is 03:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy