perl finds bug in fgrep(1)!

Daniel R. Levy levy at ttrdc.UUCP
Sat Aug 27 09:00:44 AEST 1988


In article <163 at ispi.UUCP>, jbayer at ispi.UUCP (id for use with uunet/usenet) writes:
> In article <458 at tauros.UUCP>, treval at tauros.UUCP (Trevor Luker) writes:
> ] 	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->	$
> I tried the same thing on Xenix 2.2.3.  It worked fine.

Ditto on AT&T 3B20 running SVR2.

Are you sure it isn't fgrep munging its argument somehow, or the ps finishing
(with buffered output waiting to come through the pipe) before the fgrep has
been exec'd?  Try these:

$ ps -ef | grep ps
$ ps -ef | fgrep ps

$ sleep 30 xxxxxx &	#sleep ignores extra arguments
$ ps -ef | fgrep xxxxxx	#do you see at least the sleep process?
-- 
|------------Dan Levy------------|  THE OPINIONS EXPRESSED HEREIN ARE MINE ONLY
| Bell Labs Area 61 (R.I.P., TTY)|  AND ARE NOT TO BE IMPUTED TO AT&T.
|        Skokie, Illinois        | 
|-----Path:  att!ttbcad!levy-----|



More information about the Comp.unix.wizards mailing list