Sponsored Content
Full Discussion: Grep a pattern in gz file
Top Forums UNIX for Dummies Questions & Answers Grep a pattern in gz file Post 302263395 by Autocross.US on Monday 1st of December 2008 01:16:54 PM
Old 12-01-2008
Is zcat available on your system:

zcat filename.gz | grep pattern_to_match
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

grep pattern in a file not working. please help...

Guys, I have my.mrk file as follows: rs112 rs105 rs154 rs136 ... and my.map file: 7 rs112 0.59 7 rs188 0.63 7 rs105 0.77 7 rs113 0.84 7 rs154 0.92 7 rs111 1.46 7 rs095 1.71 (3 Replies)
Discussion started by: Zoho
3 Replies

2. UNIX for Dummies Questions & Answers

Grep in a file for a particular pattern in a particular position witihn the file

Assume I have a file with a lot of data sets like 123 abc 01 456 def 02 789 ghi and I only want to grep all that datasets from my file having the pattern '02' at the postion 9-10 to get only 456 def 02 So I could group the datsets into three files according to the position 9-10, one... (9 Replies)
Discussion started by: ABE2202
9 Replies

3. Shell Programming and Scripting

Want to grep exact pattern from file

Contents of my file is: DI DI DIR PHI I want to extract only DI. I am using below command grep -w DI <file> but it is also extracting DI. Can i use any other command to extract exact pattern where '[' does not have special meaning (4 Replies)
Discussion started by: nehashine
4 Replies

4. Shell Programming and Scripting

Grep pattern from different file and display if it exists in the required file

Hi, I have two files say xxx.txt and yyy.txt. xxx.txt is with list of patterns within double quotes. Eg. "this is the line1" "this is the line2" The yyy.txt with lot of lines. eg: "This is a test message which contains rubbish information just to fill the page which is of no use. this is... (3 Replies)
Discussion started by: abinash
3 Replies

5. Shell Programming and Scripting

Grep a pattern given in one file at other file and display its corresponding contents as output.

***************************************** Right now i have this current system. I have two files say xxx.txt and yyy.txt. xxx.txt is with list of patterns within double quotes. Eg. "this is the line1" "this is the line2" The yyy.txt with lot of lines. eg: "This is a test message which... (7 Replies)
Discussion started by: abinash
7 Replies

6. Shell Programming and Scripting

Issue with grep using pattern from file

I'm trying to read in a list of text strings from a file, then use that string as a grep pattern. I am getting partial matching, which I believe stems from the linefeed at the end of each line of text. What I have now is: while read line; do echo $line; grep -i $line... (1 Reply)
Discussion started by: rogowar
1 Replies

7. Shell Programming and Scripting

script to grep a pattern from file compare contents with another file and replace

Hi All, Need help on this I have 2 files one file file1 which has several entries as : define service{ hostgroup_name !host1,!host5,!host6,.* service_description check_nrpe } define service{ hostgroup_name !host2,!host4,!host6,.* service_description check_opt } another... (2 Replies)
Discussion started by: namitai
2 Replies

8. UNIX for Dummies Questions & Answers

Problem with grep from pattern file with if

I have two sets of data accept.txt is the list of 50 words Tom Anne James ... and I have a file01.txt which has the frequency of words which I got it using cat main.file | tr -d '' | tr ' ' '\n' | tr 'A-Z' 'a-z' | sort | uniq -c | sort -n -r > file01.txt so my file now looks like this... (2 Replies)
Discussion started by: A-V
2 Replies

9. Shell Programming and Scripting

Grep a file pattern in another

Hi I'm new to the forum, so I'd apologize for any error in the format of the post. I'm trying to find a file content in another one using: grep -w -f file1 file2 file1 GJA7 TSC file 2 GJC1 GJA7 TSC1 TSC (11 Replies)
Discussion started by: flyfisherman
11 Replies

10. Shell Programming and Scripting

sed and awk usage to grep a pattern 1 and with reference to this grep a pattern 2 and pattern 3

Hi , I have a file where i have modifed certain things compared to original file . The difference of the original file and modified file is as follows. # diff mir_lex.c.modified mir_lex.c.orig 3209c3209 < if(yy_current_buffer -> yy_is_our_buffer == 0) { --- >... (5 Replies)
Discussion started by: breezevinay
5 Replies
compress(1)							   User Commands						       compress(1)

NAME
compress, uncompress, zcat - compress, uncompress files or display expanded files SYNOPSIS
compress [-fv] [-b bits] [file...] compress [-cfv] [-b bits] [file] uncompress [-cfv] [file...] zcat [file...] DESCRIPTION
compress The compress utility will attempt to reduce the size of the named files by using adaptive Lempel-Ziv coding. Except when the output is to the standard output, each file will be replaced by one with the extension .Z, while keeping the same ownership modes, change times and mod- ification times. If appending the .Z to the file pathname would make the pathname exceed 1023 bytes, the command will fail. If no files are specified, the standard input will be compressed to the standard output. 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(1)) and it takes less time to compute. The bits parameter specified during compression is encoded within the compressed file, along with a magic number to ensure that neither decompression of random data nor recompression of compressed data is subsequently allowed. uncompress The uncompress utility will restore files to their original state after they have been compressed using the compress utility. If no files are specified, the standard input will be uncompressed to the standard output. This utility supports the uncompressing of any files produced by compress. For files produced by compress on other systems, uncompress sup- ports 9- to 16-bit compression (see -b). zcat The zcat utility will write to standard output the uncompressed form of files that have been compressed using compress. It is the equiva- lent of uncompress -c. Input files are not affected. OPTIONS
The following options are supported: -c Writes to the standard output; no files are changed and no .Z files are created. The behavior of zcat is identical to that of `uncompress -c'. -f When compressing, forces compression of file, even if it does not actually reduce the size of the file, or if the corresponding file.Z file already exists. If the -f option is not given, and the process is not running in the background, prompts to verify whether an existing file.Z file should be overwritten. When uncompressing, does not prompt for overwriting files. If the -f option is not given, and the process is not running in the background, prompts to verify whether an existing file should be over- written. If the standard input is not a terminal and -f is not given, writes a diagnostic message to standard error and exits with a status greater than 0. -v Verbose. Writes to standard error messages concerning the percentage reduction or expansion of each file. -b bits Sets the upper limit (in bits) for common substring codes. bits must be between 9 and 16 (16 is the default). Lowering the number of bits will result in larger, less compressed files. OPERANDS
The following operand is supported: file A path name of a file to be compressed by compress, uncompressed by uncompress, or whose uncompressed form is written to standard out by zcat. If file is -, or if no file is specified, the standard input will be used. USAGE
See largefile(5) for the description of the behavior of compress, uncompress, and zcat when encountering files greater than or equal to 2 Gbyte ( 2**31 bytes). ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of compress, uncompress, and zcat: LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH. EXIT STATUS
The following error values are returned: 0 Successful completion. 1 An error occurred. 2 One or more files were not compressed because they would have increased in size (and the -f option was not specified). >2 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ |CSI |Enabled | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
ln(1), pack(1), attributes(5), environ(5), largefile(5), standards(5) DIAGNOSTICS
Usage: compress [-fvc] [-b maxbits] [file... ] Invalid options were specified on the command line. Missing maxbits Maxbits must follow -b, or invalid maxbits, not a numeric value. file: not in compressed format The file specified to uncompress has not been compressed. file: compressed with xxbits, can only handle yybits 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: 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 is corrupted. Compression: xx.xx% Percentage of the input saved by compression. (Relevant only for -v.) - - not a regular file: unchanged When the input file is not a regular file, (such as a directory), it is left unaltered. - - has xx other links: unchanged The input file has links; it is left unchanged. See ln(1) for more information. - - file unchanged No savings are achieved by compression. The input remains uncompressed. filename too long to tack on .Z The path name is too long to append the .Z suffix. NOTES
Although compressed files are compatible between machines with large memory, -b 12 should be used for file transfer to architectures with a small process data space (64KB or less). compress should be more flexible about the existence of the .Z suffix. SunOS 5.10 9 Sep 1999 compress(1)
All times are GMT -4. The time now is 03:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy