Sponsored Content
Top Forums Shell Programming and Scripting awk & zcat not working together Post 302793679 by RudiC on Saturday 13th of April 2013 04:39:59 AM
Old 04-13-2013
Your code can't work for several reasons.
Code:
awk 'FNR==1 {++counter}                      # fine, you count no. of files
     counter ==2 {BB[$1]=1; next}            # from the second file, keep $1. But, there's no second file, as scrutinizer pointed out.
     substr($0,26,2) =="01") {next}          # is never met in your sample input, which is fine if you want to keep all lines. One closing paranthesis too many!
     (substr($0,28,12) ~ "^[A-Z,a-z]") {next}   # would succeed on your tar's second input line if you came that far
     (substr($0,184,3) in BB) {next}         # your longest line has 177 chars
     1
    ' bb.txt                                 # just one file to work upon; see scrutinizer's post

All your code does is print your bb.txt lines.

If you need further help, specify what output you want from which input based on which logic, in plain English.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Awk: Version && nextfile

How can I find which version of Awk is installed? OpSystem is HPUX 11.x I am getting an error when trying to use the keyword nextfile and I dont know why! (Well, I can only assume that I have am using a version of Awk that does not support nextfile. However, according to O'Reilly, nextfile is... (3 Replies)
Discussion started by: google
3 Replies

2. UNIX for Dummies Questions & Answers

zcat --> Arg list too long

Hi all I have more than 1000 files in a folder and when ever i use a "compress" or "zcat" command it give error /bin/zcat: Arg list too long. . any solution for this :o (3 Replies)
Discussion started by: muneebr
3 Replies

3. Linux

zcat on Linux

Hi I am trying to extract a <filename>.tar.Z on a SLES machine using zcat. The command I am using is zcat <filename>.tar.Z | tar xf - When I use the above I get the following message tar: Read 7168 bytes from - I think the message is benign because I see that my files where... (2 Replies)
Discussion started by: felixmat1
2 Replies

4. UNIX for Advanced & Expert Users

Awk expressions working & not working

Hi, Putting across a few awk expressions. Apart from the last, all of them are working. echo a/b/c | awk -F'/b/c$' '{print $1}' a echo a/b/c++ | awk -F'/b/c++' '{print $1}' a echo a/b/c++ | awk -F'/b/c++$' '{print $1}' a/b/c++ Request thoughts on why putting a '$' post double ++... (12 Replies)
Discussion started by: vibhor_agarwali
12 Replies

5. Shell Programming and Scripting

zcat two files

Hi, Like cat file1 file2 > file Can I do zcat file1.gz file2.gz > file.gz (11 Replies)
Discussion started by: jacobs.smith
11 Replies

6. Shell Programming and Scripting

BASH ZCAT EGREP Shell Script

I created a backup script that emails all the admins when the backup is complete and attaches a log file of what what backed up. On occasion, something happens in which the backups stop working, I started "grep"ing around /var/log/syslog and I usually find the smoking gun. My goal is to zcat... (8 Replies)
Discussion started by: metallica1973
8 Replies

7. UNIX for Dummies Questions & Answers

How zcat works?

Hi, just i would like to know, how will be the response if you try to read a 40GB compressed file using zcat. a)Uncompress the 40GB file and have it in the disk. use cat to view the steps. b)Use zcat directly to view the compressed file? What are the steps being occurred in step (b)? Where... (3 Replies)
Discussion started by: pandeesh
3 Replies

8. Shell Programming and Scripting

awk Help: quick and easy question may be: How to use &&

Hi Guru's. I am trying to use to check if $5 is greater than 80 & if not 100, then to print $0 : awk '{ if ($5>80) && if ($5 != 100) print $0} But getting error: >bdf1|sed 's/%//g'|awk '{ if ($5>80) && if ($5 != 100) print $0}' syntax error The source line is 1. The error... (6 Replies)
Discussion started by: rveri
6 Replies

9. Shell Programming and Scripting

[zcat] [gunzip -c] header

Hello, When i lauches this command ssh -n server_name gunzip -c "/REP/xxxx.gz" > server.logThere are a few stray characters like NULNULNULNUL100644 NUL000000NUL000000NUL00024002704 12135060747 012607NUL at the beginning of server.log. In the xxxx.gz there is a tar file I'm not sure but it... (5 Replies)
Discussion started by: amazigh42
5 Replies

10. Solaris

ZCAT xxx.Z|tar -xvf - decompression slow ?

I have recently built a new server and patched Soalris 10 up tp latest bundle etc... When I run a decompress using the format zcat fred.Z |tar -xvf - it runs at a very slow rate. A similiar server which is less powerful runs over twice as quick. Is there any work arounds to configure decompress... (4 Replies)
Discussion started by: smcart
4 Replies
UNIQ(1) 						    BSD General Commands Manual 						   UNIQ(1)

NAME
uniq -- report or filter out repeated lines in a file SYNOPSIS
uniq [-c | -d | -u] [-i] [-f num] [-s chars] [input_file [output_file]] DESCRIPTION
The uniq utility reads the specified input_file comparing adjacent lines, and writes a copy of each unique input line to the output_file. If input_file is a single dash ('-') or absent, the standard input is read. If output_file is absent, standard output is used for output. The second and succeeding copies of identical adjacent input lines are not written. Repeated lines in the input will not be detected if they are not adjacent, so it may be necessary to sort the files first. The following options are available: -c Precede each output line with the count of the number of times the line occurred in the input, followed by a single space. -d Only output lines that are repeated in the input. -f num Ignore the first num fields in each input line when doing comparisons. A field is a string of non-blank characters separated from adjacent fields by blanks. Field numbers are one based, i.e. the first field is field one. -s chars Ignore the first chars characters in each input line when doing comparisons. If specified in conjunction with the -f option, the first chars characters after the first num fields will be ignored. Character numbers are one based, i.e. the first character is character one. -u Only output lines that are not repeated in the input. -i Case insensitive comparison of lines. DIAGNOSTICS
The uniq utility exits 0 on success, and >0 if an error occurs. COMPATIBILITY
The historic +number and -number options have been deprecated but are still supported in this implementation. SEE ALSO
sort(1) STANDARDS
The uniq utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible. HISTORY
A uniq command appeared in Version 3 AT&T UNIX. BSD
June 6, 1993 BSD
All times are GMT -4. The time now is 11:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy