Xref: utzoo comp.bugs.sys5:537 comp.unix.wizards:10717
Path: utzoo!utgpu!water!watmath!clyde!att!occrsh!rjd
From: rjd@occrsh.ATT.COM (Randy_Davis)
Newsgroups: comp.bugs.sys5,comp.unix.wizards
Subject: Re: perl finds bug in fgrep(1)!
Keywords: fgrep bug
Message-ID: <335@occrsh.ATT.COM>
Date: 26 Aug 88 23:17:45 GMT
References: <458@tauros.UUCP>
Reply-To: rjd@occrsh.UUCP (Randy_Davis)
Organization: AT&T Network & Data Systems, OKC
Lines: 18

In article <458@tauros.UUCP>, treval@tauros.UUCP (Trevor Luker) writes:
] g'day all,
] 
] 	try the following (On NCR Tower SysV.2):-
] 
] 	$ ps -ef | grep xxxxxx
] Gives->	treval  8911  8910  4 13:12:01 X00t  0:00 grep xxxxxx
] 	$ ps -ef | fgrep xxxxxx
] Gives->	$

Uh, really???  Ever thought of trying it with a different command than ps?  If
you recall, ps(1) only gives you a "snapshot" of what is going on.  I think it
is possible that it is the ps command is not showing grep because it was not
in the process table at that time.  Try "ps -ef | grep grep" a few times in a
row, and you will probably notice it not showing up every now and then,
depending on your processor.

Randy