Using Grep in a Shell Script Post: 66712

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

grep, sed in a shell script

Hi, I have a problem with a simple script I am trying to write. I want a user to type grep, sed commands that are then stored in variables. Those variables are stored in a function, and the function is then called to execute the commands. The idea is that the user does it step by step. ...

2. Shell Programming and Scripting

grep in Shell script

Hello I do want to write a script which will check any errors say "-error" in the log file then have to send email to the concern person . And the concern person will correct the error . Next time if the script runs eventhough the error has been corrected it will ...

3. Shell Programming and Scripting

Grep or Tail in shell script

Hi, I am writing a shell script that checks catalina logs on a production system and mails me if it detects errors. It greps the logs for known errors which i have defined as variables. The problem is the logs are huge, approx 30,000 before they rotate. So I am forced to use grep instead...

4. Shell Programming and Scripting

Shell script grep help

Hey there, newbie question : echo "::kmastat" | /usr/bin/mdb -k | grep Total | grep "kmem_*" Total 17326080 432853 0 Total 426508288 65458 0 Total 704757760 1572001732 0 Total ...

5. Shell Programming and Scripting

Grep command in shell script

Hi, I have written the following shell script - Error_String="error" var1="| grep -v note1 | grep -v note2" grep -i $Error_String /users/mqm/Pwork/Err/*.out $var1 The above script gives error saying "grep: can't open | grep: can't open grep grep: can't open -v" etc In my program...

6. Shell Programming and Scripting

Simple Shell Script to Grep

Hi guys, I have written this script, however the outcome is invalid. It contains grep search that is not needed: Script: #!/bin/bash #this is a test script FILES=$(ls /home/student/bin/dir1/*) GREPFUNC=$(grep -E -i "login|Successfully" ORProxyTC`date '+%m%d%Y'`*.txt/ ${FILES})...

7. Shell Programming and Scripting

How to grep sql error in shell script and exit the script?

I need help in the following script. I want to grep the sql errors insert into the error table and exit the shell script if there is any error, otherwise keep running the scripts. Here is my script #!/bin/csh -f source .orapass set user = $USER set pass = $PASS cd /opt/data/scripts echo...

8. Shell Programming and Scripting

Shell Script with Grep

Hi guys - below is my script that is checking for current file, size and timestamp. However I added a "grep" feature in it (line in red), but not getting the desired result. I am trying to acheive in output: 1. Show me the file name, timestamp, size and grep'ed words It would be a...

9. Shell Programming and Scripting

Grep in Shell script

hi guys very new to this game so excuse my ignorance. I need to create a script that simply greps for a text string and then outputs a message depending on whether the text string is there or not. The script I have setup is below, but whenever I run it I get the following error: ...

10. Shell Programming and Scripting

Speeding up shell script with grep

HI Guys hoping some one can help I have two files on both containing uk phone numbers master is a file which has been collated over a few years ad currently contains around 4 million numbers new is a file which also contains 4 million number i need to split new nto two separate files...

LEARN ABOUT HPUX

sh

sh(1)							      General Commands Manual							     sh(1)

NAME

       sh - overview of various system shells

SYNOPSIS

   POSIX Shell
       option] ...  string] [arg ...]

       option] ...  string] [arg ...]

   Korn Shell
       option] ...  string] [arg ...]

       option] ...  string] [arg ...]

   C Shell
       [command_file] [argument_list ...]

   Key Shell
DESCRIPTION

   Remarks
       The POSIX .2 standard requires that, on a POSIX-compliant system, executing the command activates the POSIX shell (located in file on HP-UX
       systems), and executing the command produces an on-line manual entry that displays the syntax of the POSIX shell command-line.

       However, the command has historically been associated with the conventional Bourne shell, which could confuse some users.   To  meet  stan-
       dards  requirements  and also clarify the relationships of the various shells and where they reside on the system, this entry provides com-
       mand-line syntax and a brief description of each shell, and lists the names of the manual entries where each shell is described in  greater
       detail.

       The Bourne shell is removed from the system starting with HP-UX 11i Version 1.5.  Please use the POSIX shell as an alternative.

   Shell Descriptions
       The HP-UX operating system supports the following shells:

	      POSIX-conforming command programming language and command interpreter
			residing  in  file Can execute commands read from a terminal or a file.  This shell conforms to current POSIX standards in
			effect at the time the HP-UX system release was introduced, and is similar to the Korn shell in many respects.	Similar in
			many  respects to the Korn shell, the POSIX shell contains a history mechanism, supports job control, and provides various
			other useful features.

	      Korn-shell command programming language and commands interpreter
			residing in file Can execute commands read from a terminal or a file.  This shell, like the POSIX shell, contains  a  his-
			tory mechanism, supports job control, and provides various other useful features.

	      A command language interpreter
			that incorporates a command history buffer, C-language-like syntax, and job control facilities.

	      Restricted version of the POSIX shell command interpreter.
			Sets  up  a  login  name  and  execution  environment whose capabilities are more controlled (restricted) than normal user
			shells.

	      restricted version of the Korn-shell command interpreter
			Sets up a login name and execution environment whose capabilities  are	more  controlled  (restricted)	than  normal  user
			shells.

	      An extension of the standard Korn Shell
			that uses hierarchical softkey menus and context-sensitive help.

							  +--------------+--------------------+
							  | To obtain:	 |  Use the command:  |
							  +--------------+--------------------+
							  | POSIX Shell  |  /usr/bin/sh ...   |
							  | Korn Shell	 |  /usr/bin/ksh ...  |
							  | C Shell	 |  /usr/bin/csh ...  |
							  | Key Shell	 |  /usr/bin/keysh    |
							  +--------------+--------------------+
       These shells can also be the default invocation, depending on the entry in the file.  See also chsh(1).

WARNINGS

       Many manual entries contain descriptions of shell behavior or describe program or application behavior similar to ``the shell'' with a ref-
       erence to ``see sh(1)''.

SEE ALSO

       For more information on the various individual shells, see:

       keysh(1)       Key Shell description.

       ksh(1)	      Korn Shell description.

       sh-posix(1)    POSIX Shell description.

       csh(1)	      C Shell description.

																	     sh(1)