Solaris

Hello,

I have spent considerable amount of time breaking my head on this and reached out here. here is the back ground.

OS - Solaris 10

There are two strings '<Orin>sop' and '<Dup>two' which I wanted to look for in a file without the quotes on different lines and ONLY if both strings are present then give me count or output something as I just need to know if both are present or not.

Can someone advise on how to do this?

FYI - tried below but its acting more an OR condition and giving output if atleast one of the string is found.

Code:

egrep -e '<Orin>sop|<Dup>two' /opt/SampleData.txt

Moderator's Comments:

Please use CODE tags when displaying sample input, sample output, and code segments.

filters are your friend.

Assuming an "old world" fgrep.... then:

Code:

fgrep -l '<Orin>sop' list-of-files-goes-here... /dev/null | tr '\012' '\000' |
   xargs -0 fgrep -l '<Dup>two'

Some explanation. I wrote this to handle weird file as the "list-of-files-goes-here"... I wanted what I wrote to work for files with spaces in their names or other strange characters.

First fgrep finds one string, returns list of files which I then null terminate the file names, and pass into a second fgrep using xargs -0 and that should return a list of file where both strings were found.

Update: You don't need the /dev/null above... I was writing originally for really really old Unix.

thanks, I have tried this but unfortunately this throws the following error
xargs: illegal arguments --0

Any suggestions?

I would try using a single awk (or on Solaris/SunOS systems /usr/xpg4/bin/awk or nawk) script instead of trying to compare outputs from two fgrep commands:

Code:

#!/bin/ksh
if [ $# -lt 1 ]
then	printf 'Usage: %s file...\n' "${0##*/}" >&2
	exit 1
fi
/usr/xpg4/bin/awk '
function check() {
	if(f1 && f2)
		print fn
	fn = FILENAME
	f1 = f2 = 0
}
FNR == 1 {
	check()
}
/<Orin>sop/ {
	f1 = 1
}
/<Dup>two/ {
	f2 = 1
}
END {	check()
}' "$@"

But, if you want to do it using fgrep, you could try something like:

Code:

#!/bin/ksh
if [ $# -lt 1 ]
then	printf 'Usage: %s file...\n' "${0##*/}" >&2
	exit 1
fi
fgrep -l '<Orin>sop' "$@" | sort -r > match1.$$
fgrep -l '<Dup>two' "$@" > match2.$$
fgrep -xf match1.$$ match2.$$
rm -rf match[12].$$

Note that I don't believe that the sort -r half of the pipeline with the 1st fgrep should be needed, but on some systems (including Apple OS X which uses a BSD based grep utility), the command:

Code:

fgrep -x -e pattern -e pattern2 file

will not print lines in file matching pattern2 if pattern is a string matching an initial substring of pattern2. But, if the order of those matching patterns is reversed, it correctly finds all of the matching lines. I don't know if the Solaris fgrep suffers from this issue or not, but with the sort -r, the problem should be avoided if it does exist.

Note also that the 2nd script takes fewer lines (and is 35 characters shorter), running 3 fgrep commands and an rm command (not counting the sort that might not be needed depending on how fgrep -x works on your system) will take longer to run than one invocation of awk unless you are processing LARGE files and the patterns you're looking for appear early in the files. On systems where awk includes the nextfile command, that difference could be removed, but awk, nawk, and /usr/xpg4/bin/awk on Solaris systems do not provide do not provide that extension.

Code:

awk '/<Orin>sop/ {f1=1} /<Dup>two/ {f2=1} f1+f2==2 {print; exit}' /opt/SampleData.txt

I apologize. The scripts I provided in post #4 in this thread solve the problem cjcox mentioned for the case where you are trying to determine which files (in a list of one or more files) contain both strings (not necessarily on the same line). Both of those scripts print the names of files (presented as operands to the script) that contain both strings.

If you are just trying to determine if a single file contains both strings, MadeInGermany's suggestion (using /usr/xpg4/bin/awk or nawk instead of awk) would be more efficient.