How to pass shell variables to awk's pattern? Post: 302450378

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to pass Shell variables to sqlplus use them as parameters

Hi, I am trying to pass some of the variables in my shell scripts to the sqlplus call and use them as parameters. For example, I would like to replace the 'SAS', and '20050612' with $var1 and $var2, respectively, how can I do that? --------------------------------------------------------...

2. AIX

how to pass variables surrounded in double quotes to awk?

Hi, I'm making progress on this but hung up on one last detail. I'd like to use AWK to pass the system date and time(among other things) to the first line of a file. Here's what I have: BEGIN {TOTALPP = 0;FREEPP=0;USEDPP=0;print "LPAR NAME:",lpar,"DATE:",tdate } I call AWK with the...

3. Shell Programming and Scripting

pass perl variables to shell script

I have a perl script that opens a text file containing numbers on each line: for example: 755993 755994 755995 755996 755997 755998 The perl script takes these numbers and store them as an array @raw_data, where I can access individual numbers by using $raw_data for the value 755993....

4. Shell Programming and Scripting

Text pattern with AWK and variables

How to to pass variable to the below awk command I would like to pass variables to the awk command instead of the constants "a/cc" but I don't know exactly the correct syntax awk '/a/,/cc/' temp1.out file.txt a b s cc g d output a b s

5. Shell Programming and Scripting

print pattern between two variables awk sed

I am trying to print text between two variables in a file I have tried the following things but none seem to work: awk ' /'$a'/ {flag=1;next} /'$b'/{flag=0} flag { print }' file and also sed "/$a/,/$b/p" file But none seem to work Any Ideas? Thanks in Advance

6. UNIX for Advanced & Expert Users

use of variables in awk to search for pattern from a file

Hi, I need to extract all the content between two strings stored in two variables "startstring" and "endstring" startstring=hello enstring=world #notworking awk '/$startstring/, $NF ~ /$endstring/ ' file > file2 The above code is not working with variables. It works when actual string...

7. UNIX for Dummies Questions & Answers

Pass variables from a text file to a shell script

Hi, I have a text file as follows: a.txt ------ STEPS=3 STEP_DURATION=100 INTERVAL=60 I want to use these values in a shell script. How to go about this?

8. UNIX for Dummies Questions & Answers

How to write Config shell script to pass variables in master shell script?

Dear Unix gurus, We have a config shell script file which has 30 variables which needs to be passed to master unix shell script that invokes oracle database sessions. So those 30 variables need to go through the database sessions (They are inputs) via a shell script. one of the variable name...

9. Shell Programming and Scripting

How to write config shell script to pass variables in master shell script?

10. Shell Programming and Scripting

awk - using variables in pattern which contain full pathname

Hello. I would like to make this bash command working. In the following code, the bash variable 'ZYPPER_LOCAL_REP' contain a full pathname like '/path/to/path/somewhere' The command list all available repositories, search for the string 'zipper_local' then on the same line search for...

LEARN ABOUT OPENSOLARIS

fgrep

fgrep(1)							   User Commands							  fgrep(1)

NAME

       fgrep - search a file for a fixed-character string

SYNOPSIS

       /usr/bin/fgrep [-bchilnsvx] -e pattern_list [file...]

       /usr/bin/fgrep [-bchilnsvx] -f file [file...]

       /usr/bin/fgrep [-bchilnsvx] pattern [file...]

       /usr/xpg4/bin/fgrep [-bchilnqsvx] -e pattern_list [-f file]
	    [file...]

       /usr/xpg4/bin/fgrep [-bchilnqsvx] [-e pattern_list] -f file
	    [file...]

       /usr/xpg4/bin/fgrep [-bchilnqsvx] pattern [file...]

DESCRIPTION

       The  fgrep (fast grep) utility searches files for a character string and prints all lines that contain that string. fgrep is different from
       grep(1) and from egrep(1) because it searches for a string, instead of searching for a pattern that matches an  expression.  fgrep  uses  a
       fast and compact algorithm.

       The characters $, *, [, ^, |, (, ), and  are interpreted literally by fgrep, that is, fgrep does not recognize full regular expressions as
       does egrep. These characters have special meaning to the shell. Therefore, to be safe, enclose the entire string within single quotes (a').

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

OPTIONS

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

       -b		  Precedes each line by the block number on which the line was found. This can be useful in locating block numbers by con-
			  text. The first block is 0.

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

       -e pattern_list	  Searches for a string in pattern-list. This is useful when the string begins with a -.

       -f pattern-file	  Takes the list of patterns from pattern-file.

       -h		  Suppresses printing of files when searching multiple files.

       -i		  Ignores upper/lower case distinction during comparisons.

       -l		  Prints the names of files with matching lines once, separated by new-lines. Does not repeat the names of files when  the
			  pattern is found more than once.

       -n		  Precedes each line by its line number in the file. The first line is 1.

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

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

       -x		  Prints only lines that are matched entirely.

   /usr/xpg4/bin/fgrep
       The following options are supported for /usr/xpg4/bin/fgrep only:

       -q    Quiet.  Does  not	write  anything  to  the standard output, regardless of matching lines. Exits with zero status if an input line is
	     selected.

OPERANDS

       The following operands are supported:

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

   /usr/bin/fgrep
       pattern	  Specifies a pattern to be used during the search for input.

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

USAGE

       See largefile(5) for the description of the behavior of fgrep 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 fgrep:  LC_COLLATE,	LC_CTYPE,  LC_MES-
       SAGES, and NLSPATH.

EXIT STATUS

       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.

ATTRIBUTES

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

   /usr/bin/fgrep
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+

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

SEE ALSO

       ed(1), egrep(1), grep(1), sed(1), sh(1), attributes(5), environ(5), largefile(5), XPG4(5)

NOTES

       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/fgrep
       The  /usr/xpg4/bin/fgrep  utility  is identical to /usr/xpg4/bin/grep -F (see grep(1)). Portable applications should use /usr/xpg4/bin/grep
       -F.

SunOS 5.11							    24 Mar 2006 							  fgrep(1)