From owner-freebsd-hackers  Tue Jan 23 13:32:25 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA18822
          for hackers-outgoing; Tue, 23 Jan 1996 13:32:25 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA18804
          for <hackers@freebsd.org>; Tue, 23 Jan 1996 13:32:16 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id OAA26295; Tue, 23 Jan 1996 14:34:19 -0700
Date: Tue, 23 Jan 1996 14:34:19 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199601232134.OAA26295@rocky.sri.MT.net>
To: Terry Lambert <terry@lambert.org>
Cc: hackers@freebsd.org
Subject: Re: recursive grep
In-Reply-To: <199601231734.KAA17822@phaeton.artisoft.com>
References: <199601230131.RAA11361@paris.CS.Berkeley.EDU>
	<199601231734.KAA17822@phaeton.artisoft.com>
Sender: owner-hackers@freebsd.org
Precedence: bulk

Terry Lambert writes:
> The GNU derived find doesn't flush its output, so if you were to pipe
> it at that point (and use -print instead of a "/dev/null" argument to
> get the name), you would have your output screwed.

Except that we're not using the GNU derived find, and we've fixed the
bug in the BSD find you are complaining about a *long* time ago.

revision 1.5
date: 1995/09/12 23:15:33;  author: nate;  state: Exp;  lines: +3 -0
Simpler fix to the find bug reported by Terry Lambert
<terry@lambert.org>
 
[ Find to a file vs. to stdout ] produces different output because find
does not flush stdout when doing a -print.
 
Submitted by:   Jeffrey Hsu <hsu@freefall.freebsd.org>

You're even mentioned in the log. :)


Nate