Bash - CLI - grep - Passing result to grep through pipe Post: 302632299

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

grep to handle a 0 result

Hi guys, I have the following grep command in a script to search through a file for a string and return its count, and it works fine for when the string exists: grep "string" file.txt | wc However, sometimes the result will be 0 and I want the script to take this as the result. Right now...

2. Shell Programming and Scripting

diaplaying the grep result

Hi, My code is like this if swlist -a revision 2>/dev/null | grep ABC 2>/dev/null then echo "Found Above mentioned ABC Version, please remove it first..." fi This is displaying the result to the screen. i want to first suppress that and for that i wrote the below...

3. Shell Programming and Scripting

How to negate grep result?

Here is my script so far: set dirs = ` find . -name "message.jar" 2> /dev/null | cut -d "/" -f 2 ` | uniq foreach dir ( $dirs ) if (grep $dir/* someText==null) --> how do I write this in script? print $dir end end

4. Shell Programming and Scripting

pipe result from grep

Trying to create a command line script to look for all files matching a pattern, grep for a specific value in each file, and write out the filename long list. It's possible the filename won't containe the value. { echo �Running....� for fname in 811_Intermediate_File_* do grep -l...

5. UNIX for Dummies Questions & Answers

grep, expecting 1 result, getting more

Hi Please take a look below, I'm grepping for /app/oracle and would like explicitly that result and not /app/oracle/admin as well. # cat /tmp/fs.list /app/oracle /app/oracle/admin # cat /tmp/fs.list | grep -w "/app/oracle" /app/oracle /app/oracle/admin

6. Shell Programming and Scripting

Passing variables from bash to php-cli

Hello everyone, I've been looking how to pass variables between bash and php-cli in 1 file. So far i got this: #!/bin/bash echo "This is bash" php << EOF <?php echo "This is php\n"; ?> EOF I would now like to be able to pass a variable declared in the bash to the php. I already...

7. UNIX for Dummies Questions & Answers

Pipe grep to rm

We have a number of OS X 10.6 machines who have home folders with incorrect permissions, which are causing managed prefs not to be applied correctly and not allowing saving. I need to delete all home folders whose name is numerical and modified before a certain date. I'm not sure of the date part...

8. Solaris

grep result in newline

Hi While trying to do a search on solaris, the grep results seems to be appearing on the same line instead of the new line. Wed Jan 18 14:45:48 weblogic@test:/abcd$ grep qainejb02 * qa_cluster_biz_view_tc_intl_servers_ports_2:qainejb02 7101 qa_cluster_servers_2:qainejb02...

9. Shell Programming and Scripting

pipe to grep doesn't work in bash script

Hi, I'm trying to write a script that checks gvfs to see if a mount exists so I can run it from network-manager's status hooks. I thought I'd pipe the output of gvfs-mount -l to grep for the particular mounts I care about. When I do this in a bash script: cmnd="gvfs-mount -l | grep -i...

10. Shell Programming and Scripting

Grep result from dd command

Hi, I am running following command in a bash script for testing IO and use grep to get throughput number, but it did not work, it displayed everything: dd if=/dev/zero of=/dev/null bs=1G count=1 oflag=dsync | grep bytes | awk '{print $7}' 1+0 records in 1+0 records out 536870912 bytes...

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)

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

grep to handle a 0 result

Discussion started by: ocelot

2. Shell Programming and Scripting

diaplaying the grep result

Discussion started by: rag84dec

3. Shell Programming and Scripting

How to negate grep result?

Discussion started by: mmdawg

4. Shell Programming and Scripting

pipe result from grep

Discussion started by: gavineq