Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Translate grep to awk
Top Forums Shell Programming and Scripting Translate grep to awk Post 302752229 by Yoda on Sunday 6th of January 2013 09:25:17 AM
Old 01-06-2013
Code:
sed -n "2,10p" lfile | awk '/error/&&!/memory/{c++}END{print c}'
sed -n "2,10p" lfile | awk '/error/&&!/memory/'
sed -n "2,10p" lfile | awk '/error/&&/memory/{c++}END{print c}'
sed -n "2,10p" lfile | awk '/error/&&/memory/'

Note: You can get rid of sed as well using NR variable in awk
Code:
awk 'NR>=2&&NR<=10&&/error/&&!/memory/{c++}END{print c}' lfile
awk 'NR>=2&&NR<=10&&/error/&&!/memory/' lfile
awk 'NR>=2&&NR<=10&&/error/&&/memory/{c++}END{print c}' lfile
awk 'NR>=2&&NR<=10&&/error/&&/memory/' lfile

These 2 Users Gave Thanks to Yoda For This Post:
MattyV SkySmart
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Can someone help translate this snippet?

Hello all - This snippet from a script runs on a Tru64 machine (ksh). if ps -ef | grep thing1 | grep dtsession | grep -v grep then echo "Killing Thing1 desktop session" kill -9 'ps -ef | grep thing1 | grep dtsession | grep -v grep | awk '{FS = " "}{print $2}'' fi I'm... (7 Replies)
Discussion started by: Heron
7 Replies

2. Shell Programming and Scripting

translate rc to string

Hi Maybe you can suggest a nicer way to do the following: RET_STR=$(echo ${RET} | sed -e 's/0/Object is not mapped/' \ -e 's/1/Operation Internal Error/' \ -e 's/2/Operation Invalid Arguments/' \ -e 's/3/Object is mapped/' \ -e 's/4/Path not found/') (3 Replies)
Discussion started by: ynir
3 Replies

3. Shell Programming and Scripting

MEM=`ps v $PPID| grep -i db2 | grep -v grep| awk '{ if ( $7 ~ " " ) { print 0 } else

Hi Guys, I need to set the value of $7 to zero in case $7 is NULL. I've tried the below command but doesn't work. Any ideas. thanks guys. MEM=`ps v $PPID| grep -i db2 | grep -v grep| awk '{ if ( $7 ~ " " ) { print 0 } else { print $7}}' ` Harby. (4 Replies)
Discussion started by: hariza
4 Replies

4. Shell Programming and Scripting

Read content between xml tags with awk, grep, awk or what ever...

Hello, I trying to extract text that is surrounded by xml-tags. I tried this cat tst.xml | egrep "<SERVER>.*</SERVER>" |sed -e "s/<SERVER>\(.*\)<\/SERVER>/\1/"|tr "|" " " which works perfect, if the start-tag and the end-tag are in the same line, e.g.: <tag1>Hello Linux-Users</tag1> ... (5 Replies)
Discussion started by: Sebi0815
5 Replies

5. UNIX for Dummies Questions & Answers

Help translate code

Hi, all of you!!! I have this code and I won to build-in some more code. I know this is a lot of code. if ; then if ; then SYSROOT="$1" S_SCRIPT="cd $1 ; ./etc/rc.sysinit 2>&1 &" fi else ... (22 Replies)
Discussion started by: jokerper
22 Replies

6. Shell Programming and Scripting

translate this string

Hi, I'm using code below to assign title for Putty Window to show user@hostname+curr directory. Trying to read this "write only" language, can anybody help me to go thru this string, too many thing in it I can't expaing Tx T export PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}:... (1 Reply)
Discussion started by: trento17
1 Replies

7. Shell Programming and Scripting

translate sed to awk

hi, can someone tell me how can I translate the following line from sed to awk? `sed 's/^*:*:*:*:*:\(*\):.*/\1/ How to use code tags when posting data and code samples. (14 Replies)
Discussion started by: adam25bc
14 Replies

8. Shell Programming and Scripting

AWK/GREP: grep only lines starting with integer

I have an input file 12.4 1.72849432773174e+01 -7.74784188610632e+01 12.5 9.59432114416327e-01 -7.87018212757537e+01 15.6 5.20139995965960e-01 -5.61612429666624e+01 29.3 3.76696387248366e+00 -7.42896194101892e+01 32.1 1.86899877018077e+01 -7.56508762501408e+01 35 6.98857157014640e+00... (2 Replies)
Discussion started by: chrisjorg
2 Replies

9. UNIX for Dummies Questions & Answers

Piping grep into awk, read the next line using grep

Hi, I have a number of files containing the information below. """"" Fundallinfo 6.3950 14.9715 14.0482 """"" I would like to grep for Fundallinfo and use it to read the next line? I ideally would like to read the three numbers that follow in the next line and... (2 Replies)
Discussion started by: Paul Moghadam
2 Replies

10. Shell Programming and Scripting

Translate bash mathematical calculation to awk

this code below is very useful in calculating mean and quartiles. however, i would really like to translate it to awk without having to write to any external file: #!/bin/sh filename="tmp.txt" sort -n $1 >$filename rows=`wc -l $filename|cut -d' ' -f1` q2=`echo "($rows+1)/2" |bc` ... (3 Replies)
Discussion started by: SkySmart
3 Replies

LEARN ABOUT SUNOS

egrep

egrep(1)																  egrep(1)

NAME

       egrep - search a file for a pattern using full regular expressions

SYNOPSIS

       /usr/bin/egrep [-bchilnsv] [-e pattern_list] [-f file] [strings] [file...]

       /usr/xpg4/bin/egrep [-bchilnsvx] [-e pattern_list] [-f file] [strings] [file...]

       The  egrep  (expression grep) utility searches files for a pattern of characters and prints all lines that contain that pattern. egrep uses
       full regular expressions (expressions that have string values that use the full set of alphanumeric and special characters)  to	match  the
       patterns.  It uses a fast deterministic algorithm that sometimes needs exponential space.

       If  no  files  are  specified,  egrep  assumes standard input. Normally, each line found is copied to the standard output. The file name is
       printed before each line found if there is more than one input file.

   /usr/bin/egrep
       The /usr/bin/egrep utility accepts full regular expressions as described on the regexp(5) manual page, except for ( and ), ( and ),	{
       and }, < and >, and 
, and with the addition of:

       1.  A full regular expression followed by + that matches one or more occurrences of the full regular expression.

       2.  A full regular expression followed by ? that matches 0 or 1 occurrences of the full regular expression.

       3.  Full regular expressions separated by | or by a NEWLINE that match strings that are matched by any of the expressions.

       4.  A full regular expression that can be enclosed in parentheses ()for grouping.

       Be careful using the characters $, *, [, ^, |, (, ), and  in full regular expression, because they are also meaningful to the shell. It is
       safest to enclose the entire full regular expression in single quotes  '... '.

       The order of precedence of operators is [], then *?+, then concatenation, then | and NEWLINE.

   /usr/xpg4/bin/egrep
       The /usr/xpg4/bin/egrep utility uses the regular expressions described in the EXTENDED REGULAR EXPRESSIONS  section of the regex(5)  manual
       page.

       The following options are supported for both /usr/bin/egrep and /usr/xpg4/bin/egrep:

       -b	       Precede each line by the block number on which it was found. This can be useful in locating block numbers by context (first
		       block is 0).

       -c	       Print only a count of the lines that contain the pattern.

       -e pattern_list Search for a pattern_list (full regular expression that begins with a -).

       -f file	       Take the list of full regular expressions from file.

       -h	       Suppress printing of filenames when searching multiple files.

       -i	       Ignore upper/lower case distinction during comparisons.

       -l	       Print the names of files with matching lines once, separated by NEWLINEs. Does not repeat the names of files when the  pat-
		       tern is found more than once.

       -n	       Precede each line by its line number in the file (first line is 1).

       -s	       Work silently, that is, display nothing except error messages. This is useful for checking the error status.

       -v	       Print all lines except those that contain the pattern.

   /usr/xpg4/bin/egrep
       The following option is supported for /usr/xpg4/bin/egrep only:

       -x	Consider only input lines that use all characters in the line to match an entire fixed string or regular expression to be matching
		lines.

       The following operands are supported:

       file	       A path name of a file to be searched for the patterns. If no file operands are specified, the standard input is used.

   /usr/bin/egrep
       pattern	       Specify a pattern to be used during the search for input.

   /usr/xpg4/bin/egrep
       pattern	       Specify one or more patterns to be used during the search for input. This operand is treated as if  it  were  specified	as
		       -epattern_list.

USAGE

       See largefile(5) for the description of the behavior of egrep when encountering files greater than or equal to 2 Gbyte ( 2**31 bytes).

       See  environ(5)	for  descriptions of the following environment variables that affect the execution of egrep: LC_COLLATE, LC_CTYPE, LC_MES-
       SAGES, and NLSPATH.

       The following exit values are returned:

       0	If any matches are found.

       1	If no matches are found.

       2	For syntax errors or inaccessible files (even if matches were found).

       See attributes(5) for descriptions of the following attributes:

   /usr/bin/egrep
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+
       |CSI			     |Not Enabled		   |
       +-----------------------------+-----------------------------+

   /usr/xpg4/bin/egrep
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWxcu4			   |
       +-----------------------------+-----------------------------+
       |CSI			     |Enabled			   |
       +-----------------------------+-----------------------------+

       fgrep(1), grep(1), sed(1), sh(1), attributes(5), environ(5), largefile(5), regex(5), regexp(5), XPG4(5)

       Ideally there should be only one grep command, but there is not a single algorithm that spans a wide enough range of space-time tradeoffs.

       Lines are limited only by the size of the available virtual memory.

   /usr/xpg4/bin/egrep
       The /usr/xpg4/bin/egrep utility is identical to /usr/xpg4/bin/grep -E (see grep(1)). Portable applications  should  use	/usr/xpg4/bin/grep
       -E.

								    23 May 2005 							  egrep(1)
All times are GMT -4. The time now is 05:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy