Date: Fri, 26 Sep 1997 18:34:49 +0930 From: Greg Lehey <grog@lemis.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Mark Murray <mark@grondar.za>, Nate Williams <nate@mt.sri.com>, FreeBSD current users <FreeBSD-current@FreeBSD.ORG> Subject: Re: find still broken - is this only happening to me? Message-ID: <19970926183449.36254@lemis.com> In-Reply-To: <8145.875264305@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Sep 26, 1997 at 10:58:25AM %2B0200 References: <19970926171729.56024@lemis.com> <8145.875264305@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 26, 1997 at 10:58:25AM +0200, Poul-Henning Kamp wrote: > In message <19970926171729.56024@lemis.com>, Greg Lehey writes: > >>>> $ find /sys -follow -name '*.[csh]' | xargs grep ENFILE|less >> >> Grrr. I went back and recompiled find with -g. And it worked. So I >> recompiled it with the default CFLAGS. And it worked. I promise, >> nothing in the source tree has changed since I built it yesterday, >> only the problem has gone into hiding. >> >> Let's forget this one. If it happens again, I'll try to catch it >> before it goes into hiding again. > > Is there any chance that you had a directory named so it matched '*.[csh]' ? > > Ie, would a > > find /sys -type f -name '*.[csh]' | xargs grep ENFILE|less > > have made a difference ? No, I've seen this in a number of places. And I repeated exactly the same command with the newly compiled version. I'm sure there *is* a bug there somewhere--recall that GNU find doesn't have the same problem--but it's obviously pretty elusive. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970926183449.36254>