perl finds bug in fgrep(1)!

Randy_Davis rjd at occrsh.ATT.COM
Sat Aug 27 09:17:45 AEST 1988


In article <458 at tauros.UUCP>, treval at 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



More information about the Comp.unix.wizards mailing list