Your shell is running out of space trying to get a list of all files in the first directory you are processing with:
Do you really need to print the name of every regular file on your system? Or, can you just print the names of the files containing the text for which you are searching along with the lines that contain the matching text in those files?
Are you searching for fixed strings, for strings matching a basic regular expression, or for strings that match an extended regular expression?
PS: Are you intentionally excluding dot files found in the root directory on your system from your search?
Last edited by Don Cragun; 08-11-2015 at 03:22 AM..
Reason: Add postscript.
Hi,
I have a cron job which executes daily once 9 PM.
The script is like
if
then
TYPE=OC
elif
then
TYPE=i
elif
then
TYPE=mmc
elif
then
TYPE=CB
elif
then
TYPE=oth
fi (1 Reply)
Hello, i am familiar enough with unix to do some damage but thats about it.
We have a set of RS/6000 43P Model 150's running AIX for our Catia V4 programmers.
back in the 90's a script was written to automate the conversion of files into machine code. that script has started giving us... (0 Replies)
How to allocate memory for a shell script on aix box at the time of execution i.e at runtime
Are there any commands for AIX in specific
Thanks in Advance (1 Reply)
Hi,
I am new to shell scripts may be the error is very very small and i am unable to catch hold of it, any suggestion would be appreciated....error is at the bottom:
+210 # get file type
+211 filetype=`tail -1 "$inputdir"/"$i"|cut -d"|" -f2`
+212 #
+213 # get the record count as specified... (4 Replies)
Hi All
I am quite new to Unix. Following is a shell script that i have written and getting the subject mentioned error.
#!/bin/ksh
#-------------------------------------------------------------------------
# File: ang_stdnld.ksh
#
# Desc: UNIX shell script to extract Store information.... (3 Replies)
Hi guys,
I hope you can help me out with this one.
I am getting an error in AIX when running my KSH script 0403-029 There is not enough memory available now.
It is getting this error at the point where I have a PL/SQL Script executed. After executing, I wanted to put it in the log file.... (4 Replies)
In AIX 5.1, a daily run script that backing up oracle data failed yesterday with following errors:
The Tivoli backup of DBPROD failed.
What could be the issue, OS, backup or Oracle? (3 Replies)
Hi,
I run an awk script and I got the error attached below:
here are the lines that the compiler point to as an error:
duration = timeEnd1-timeBegin1;
print "Transmission: type of traffic " flow1 ;
print - Total transmitted bits = totalBits1 bits;
print - duration = ... (2 Replies)
Script:
#!/sbin/sh
echo "Welcome to my First Script"
echo "Enter a word"
read PASS
if then
echo "You are correct"
elif then
echo "Thats incorrect"
else
echo "Bye"
fi
When i run the script shell says:
Syntax error at line 7:'elif' is not expected
I ran through some old posts and... (3 Replies)
I am getting the error :
rocfm/wls_subload/in/processed_files/tel_input_additional_checked_all_mandatory.txt: 0403-057 Syntax error at
line 1 : `|' is not expected.
>>>>ALL MANDATORY FIELDS CHECKING IS SUCCESSFUL count is 0
... (3 Replies)
Discussion started by: princetd001
3 Replies
LEARN ABOUT BSD
fgrep
GREP(1) General Commands Manual GREP(1)NAME
grep, egrep, fgrep - search a file for a pattern
SYNOPSIS
grep [ option ] ... expression [ file ] ...
egrep [ option ] ... [ expression ] [ file ] ...
fgrep [ option ] ... [ strings ] [ file ]
DESCRIPTION
Commands of the grep family search the input files (standard input default) for lines matching a pattern. Normally, each line found is
copied to the standard output. Grep patterns are limited regular expressions in the style of ex(1); it uses a compact nondeterministic
algorithm. Egrep patterns are full regular expressions; it uses a fast deterministic algorithm that sometimes needs exponential space.
Fgrep patterns are fixed strings; it is fast and compact. The following options are recognized.
-v All lines but those matching are printed.
-x (Exact) only lines matched in their entirety are printed (fgrep only).
-c Only a count of matching lines is printed.
-l The names of files with matching lines are listed (once) separated by newlines.
-n Each line is preceded by its relative line number in the file.
-b Each line is preceded by the block number on which it was found. This is sometimes useful in locating disk block numbers by con-
text.
-i The case of letters is ignored in making comparisons -- that is, upper and lower case are considered identical. This applies to
grep and fgrep only.
-s Silent mode. Nothing is printed (except error messages). This is useful for checking the error status.
-w The expression is searched for as a word (as if surrounded by `<' and `>', see ex(1).) (grep only)
-e expression
Same as a simple expression argument, but useful when the expression begins with a -.
-f file
The regular expression (egrep) or string list (fgrep) is taken from the file.
In all cases the file name is shown if there is more than one input file. Care should be taken when using the characters $ * [ ^ | ( ) and
in the expression as they are also meaningful to the Shell. It is safest to enclose the entire expression argument in single quotes ' '.
Fgrep searches for lines that contain one of the (newline-separated) strings.
Egrep accepts extended regular expressions. In the following description `character' excludes newline:
A followed by a single character other than newline matches that character.
The character ^ matches the beginning of a line.
The character $ matches the end of a line.
A . (period) matches any character.
A single character not otherwise endowed with special meaning matches that character.
A string enclosed in brackets [] matches any single character from the string. Ranges of ASCII character codes may be abbreviated
as in `a-z0-9'. A ] may occur only as the first character of the string. A literal - must be placed where it can't be mistaken as
a range indicator.
A regular expression followed by an * (asterisk) matches a sequence of 0 or more matches of the regular expression. A regular
expression followed by a + (plus) matches a sequence of 1 or more matches of the regular expression. A regular expression followed
by a ? (question mark) matches a sequence of 0 or 1 matches of the regular expression.
Two regular expressions concatenated match a match of the first followed by a match of the second.
Two regular expressions separated by | or newline match either a match for the first or a match for the second.
A regular expression enclosed in parentheses matches a match for the regular expression.
The order of precedence of operators at the same parenthesis level is [] then *+? then concatenation then | and newline.
Ideally there should be only one grep, but we don't know a single algorithm that spans a wide enough range of space-time tradeoffs.
SEE ALSO ex(1), sed(1), sh(1)DIAGNOSTICS
Exit status is 0 if any matches are found, 1 if none, 2 for syntax errors or inaccessible files.
BUGS
Lines are limited to 256 characters; longer lines are truncated.
4th Berkeley Distribution April 29, 1985 GREP(1)