Sponsored Content
Top Forums Shell Programming and Scripting Is there any way to find the compressed size of a file without compressing it in linux Post 302527539 by DGPickett on Friday 3rd of June 2011 01:58:57 PM
Old 06-03-2011
Well, if you mean without uncompressing, it is a function of the tools that compressed the file. Check the man pages for the uncompression tool, to see if it has some list option. Also, you can uncompress to a pipe to wc: "gzcat file | wc -c | read csize", so you uncompress using CPU but need no space for the product.

If you mean the length of a potential compressed version of an uncompressed file, no, but you can do a similar pipe deal" "compress < file | wc -c | read csize"
 

10 More Discussions You Might Find Interesting

1. Solaris

command to find out total size of a specific file size (spread over the server)

hi all, in my server there are some specific application files which are spread through out the server... these are spread in folders..sub-folders..chid folders... please help me, how can i find the total size of these specific files in the server... (3 Replies)
Discussion started by: abhinov
3 Replies

2. Shell Programming and Scripting

To find the RAM size for an Linux server.

Hi Gurus, Can someone let me know how to find the RAM size,ROM size and Number of processors for a linux server. Version :Linux 2.4.9-e.57smp Also what does "e.57smp" stands for? Thanks in advance gurus..... cheers. (3 Replies)
Discussion started by: navojit dutta
3 Replies

3. Shell Programming and Scripting

find file size

My Question is ----------------- Assume you've a directory (i.e /home/test/) which contains n number of files, rename all the files which has byte count more than zero (0) with .bak extension. Write shell script to achieve this output, execute the same without using". / " in front of... (6 Replies)
Discussion started by: hgriva1
6 Replies

4. Shell Programming and Scripting

How to find size of a file

Hi, I have to directory /usr/inbound ------------- 10900.txt 10889.txt 109290202.txt I need to create inbound directory and i need to know size of these files one by one if file size is zero i need to print message like "empty file" Please help me how to solve this thanks krish. (4 Replies)
Discussion started by: kittusri9
4 Replies

5. Shell Programming and Scripting

find with file size and show the size

Hi All... is the below command be modified in sucha way that i can get the file size along with the name and path of the file the below command only gives me the file location which are more than 100000k...but I want the exact size of the file also.. find / -name "*.*" -size +100000k ... (3 Replies)
Discussion started by: rpraharaj84
3 Replies

6. Shell Programming and Scripting

Find all tar and compressed file

Hi, I'm trying to find all tar and compressed files (say gzip). I'm having to assume that the tar and gzip files may or may not have the correct extension (.tar .gz .tgz etc). Any help appreciated (2 Replies)
Discussion started by: andyatit
2 Replies

7. AIX

Compressing the files subject to size - Urgent help

Dear All, I have hunderds of files. I just want to compress all the files which limits to 4GB. that is need compress the files and the zip file should not exceed the 4gb. Can please give me solution for that. Thanks in advance. Kishore (1 Reply)
Discussion started by: tvbhkishore
1 Replies

8. Linux

Find Page size in linux

Hi, How do i find Linux kernel page size using command ? Thanks in advance. (1 Reply)
Discussion started by: forumguest
1 Replies

9. Filesystems, Disks and Memory

Compressed Filesystem for Linux

Hi Everybody: I'm searching a compressed Filesystem for a external disk, what I use for a full, diary and differential Backup. The performance is not important, I search the best option for compress data, but I want have access to structure disk, with directories and files in the Backup disk.... (6 Replies)
Discussion started by: bypper
6 Replies

10. UNIX for Dummies Questions & Answers

Size of compressed file

Hi All, Is there is any way to find the size of compressed file without doing decompression. The size should give the original uncompressed data size Thanks Arun (3 Replies)
Discussion started by: arunkumar_mca
3 Replies
COMPRESS(1)						      General Commands Manual						       COMPRESS(1)

NAME
compress, uncompress, zcat - compress and expand data (version 4.1) SYNOPSIS
compress [ -f ] [ -v ] [ -c ] [ -V ] [ -r ] [ -b bits ] [ name ... ] uncompress [ -f ] [ -v ] [ -c ] [ -V ] [ name ... ] zcat [ -V ] [ name ... ] DESCRIPTION
Compress reduces the size of the named files using adaptive Lempel-Ziv coding. Whenever possible, each file is replaced by one with the extension .Z, while keeping the same ownership modes, access and modification times. If no files are specified, the standard input is com- pressed to the standard output. Compress will only attempt to compress regular files. In particular, it will ignore symbolic links. If a file has multiple hard links, compress will refuse to compress it unless the -f flag is given. If -f is not given and compress is run in the foreground, the user is prompted as to whether an existing file should be overwritten. Compressed files can be restored to their original form using uncompress or zcat. uncompress takes a list of files on its command line and replaces each file whose name ends with .Z and which begins with the correct magic number with an uncompressed file without the .Z. The uncompressed file will have the mode, ownership and timestamps of the compressed file. The -c option makes compress/uncompress write to the standard output; no files are changed. zcat is identical to uncompress -c. zcat uncompresses either a list of files on the command line or its standard input and writes the uncompressed data on standard output. zcat will uncompress files that have the correct magic number whether they have a .Z suffix or not. If the -r flag is specified, compress will operate recursively. If any of the file names specified on the command line are directories, compress will descend into the directory and compress all the files it finds there. The -V flag tells each of these programs to print its version and patchlevel, along with any preprocessor flags specified during compila- tion, on stderr before doing any compression or uncompression. Compress uses the modified Lempel-Ziv algorithm popularized in "A Technique for High Performance Data Compression", Terry A. Welch, IEEE Computer, vol. 17, no. 6 (June 1984), pp. 8-19. 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 (default 16). Bits must be between 9 and 16. The default can be changed in the source to allow compress to be run on a smaller machine. After the bits limit is attained, 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. Note that 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 sub- strings. Typically, text such as source code or English is reduced by 50-60%. Compression is generally much better than that achieved by Huffman coding (as used in pack), or adaptive Huffman coding (compact), and takes less time to compute. Under the -v option, a message is printed yielding the percentage of reduction for each file compressed. Exit status is normally 0; if the last file is larger after (attempted) compression, the status is 2; if an error occurs, exit status is 1. SEE ALSO
pack(1), compact(1) DIAGNOSTICS
Usage: compress [-dfvcVr] [-b maxbits] [file ...] Invalid options were specified on the command line. Missing maxbits Maxbits must follow -b. file: not in compressed format The file specified to uncompress has not been compressed. file: compressed with xx bits, can only handle yy bits 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: already has .Z suffix -- no change The file is assumed to be already compressed. Rename the file and try again. file: filename too long to tack on .Z The file cannot be compressed because its name is longer than 12 characters. Rename and try again. This message does not occur on BSD systems. file already exists; do you wish to overwrite (y or n)? Respond "y" if you want the output file to be replaced; "n" if not. uncompress: corrupt input A SIGSEGV violation was detected which usually means that the input file has been corrupted. Compression: xx.xx% Percentage of the input saved by compression. (Relevant only for -v.) -- not a regular file or directory: ignored When the input file is not a regular file or directory, (e.g. a symbolic link, socket, FIFO, device file), it is left unaltered. -- has xx other links: unchanged The input file has links; it is left unchanged. See ln(1) for more information. Use the -f flag to force compression of multiply- linked files. -- file unchanged No savings is achieved by compression. The input remains virgin. BUGS
Although compressed files are compatible between machines with large memory, -b12 should be used for file transfer to architectures with a small process data space (64KB or less, as exhibited by the DEC PDP series, the Intel 80286, etc.) Invoking compress with a -r flag will occasionally cause it to produce spurious error warnings of the form "<filename>.Z already has .Z suffix - ignored" These warnings can be ignored. See the comments in compress.c:compdir() for an explanation. local COMPRESS(1)
All times are GMT -4. The time now is 06:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy