topic Usage error within script with grep/egrep in Operating System - Linux

Usage error within script with grep/egrep

erics_1 — Thu, 20 Oct 2005 11:54:36 GMT

Hello all,

I have what hopefully will be an easy fix but I haven't been able to resolve the problem yet. I have the following line in a script that gives a usage error when runnning with set -x:

ABORTED_OBJECTS=`omnirpt -report session_objects -session $SESSIONS|egrep -i 'FileSystem|RawDisk'|grep $HOST_NAME|wc -l`

I can run this omnirpt command from the command line without issue but the script shows a usage error. Any insight would be greatly appreciated.

Thanks,
Eric

Re: Usage error within script with grep/egrep

erics_1 — Thu, 20 Oct 2005 12:22:22 GMT

A bit more clarification....

The usage error comes from egrep. Here's the output from replacing egrep with grep -E:

+ grep -e FileSystem -e RawDisk
+ wc -l
+ grep
usage: grep [-E|-F] [-c|-l|-q] [-bhinsvx] -e pattern_list...
[-f pattern_file...] [file...]
usage: grep [-E|-F] [-c|-l|-q] [-bhinsvx] [-e pattern_list...]
-f pattern_file... [file...]
usage: grep [-E|-F] [-c|-l|-q] [-bhinsvx] pattern [file...]
ABORTED_OBJECTS=0

Thanks,
Eric

Re: Usage error within script with grep/egrep

Denver Osborn — Thu, 20 Oct 2005 12:26:20 GMT

Howdy Eric,

Is the usage error from omnirpt or one of the greps?

check that SESSIONS and HOST_NAME variables aren't null.

I ran a similar script on a box for testing, and it went w/ out error.

#!/bin/sh

SESSIONS="2005/10/20-1"
HOST_NAME=nodename

ABORTED_OBJECTS=`omnirpt -report session_objects -session $SESSIONS|egrep -i 'FileSystem|RawDisk'|grep $HOST_NAME|wc -l`

echo Aborted = $ABORTED_OBJECTS

hope this helps,
-denver

Re: Usage error within script with grep/egrep

Bill Hassell — Thu, 20 Oct 2005 12:30:14 GMT

This is a bit simpler and replaces the deprecated construct using grave accents with $() and splits each filter onto a separate line:

set -u
ABORTED_OBJECTS=$(omnirpt -report session_objects -session $SESSIONS \
| grep -i -e FileSystem -e RawDisk \
| grep $HOST_NAME|wc -l)

egrep (grep -E) can be used with multiple search terms but -e is a simpler method and doesn't need quoting to protect simple terms. The set -u is always desirable to protect against spelling errors. The shell will silently replace undefined variables with a null value, whereas set -u will abort the script indicating that an undefined variable was used as an argument ($HOST_NAME not spelled right or not assigned?)

Re: Usage error within script with grep/egrep

Denver Osborn — Thu, 20 Oct 2005 12:30:18 GMT

ahh... that looks like $HOST_NAME in the 2nd grep is null.

-denver

Re: Usage error within script with grep/egrep

Pat Lieberg — Thu, 20 Oct 2005 12:33:00 GMT

Do you want the output of the command assigned to the variable? If so, it should be like this:

ABORTED_OBJECTS=$(omnirpt -report session_objects -session $SESSIONS|egrep -i 'FileSystem|RawDisk'|grep $HOST_NAME|wc -l)

Re: Usage error within script with grep/egrep

Jean-Luc Oudart — Thu, 20 Oct 2005 12:34:03 GMT

If the variable exists but is empty you would get such message
May be you could put the command into a vaiable and display it before you try to evaluate it :
cmd="omnirpt -report session_objects -session $SESSIONS|egrep -i 'FileSystem|RawDisk'|grep $HOST_NAME|wc -l"
echo $cmd

Regards
Jean-Luc

Re: Usage error within script with grep/egrep

erics_1 — Thu, 20 Oct 2005 12:36:59 GMT

Good call Denver,

This script had been in place for some time. Due to the addition of some rawdisk backups, it had to be modified. Sometimes you get convinced where the problem lies and that's where you waste a lot of time. HOST_NAME hadn't been set yet which I believe will fix the usage errors. Thanks to all for your replies and time!

Best Regards,
Eric

Re: Usage error within script with grep/egrep

erics_1 — Thu, 20 Oct 2005 12:37:45 GMT

See above