Date: Fri, 26 Sep 1997 17:17:29 +0930 From: Greg Lehey <grog@lemis.com> To: Mark Murray <mark@grondar.za> Cc: 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: <19970926171729.56024@lemis.com> In-Reply-To: <19970926084641.09282@lemis.com>; from Greg Lehey on Fri, Sep 26, 1997 at 08:46:41AM %2B0930 References: <199709251615.SAA04793@greenpeace.grondar.za> <19970926084641.09282@lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 26, 1997 at 08:46:41AM +0930, Greg Lehey wrote:
> On Thu, Sep 25, 1997 at 06:15:30PM +0200, Mark Murray wrote:
>> Nate Williams wrote:
>>>> I reported this a couple of weeks ago. Has nobody else experienced it?
>>>>
>>>> $ find /sys -follow -name "*.[csh]" | xargs grep ENFILE|less
>>>> ): no beginning '('
>>>
>>> Works for me (w/out less, since I don't have it installed). No errors.
>>
>> This chap (Greg?) most likely has a funny file somewhere. Make the command
>> line:
>> $ find /sys -follow -name '*.[csh]' | xargs grep ENFILE|less
>>
>> (singe quotes, not double), and it should work. The *.[csh] is being
>> allowed to glob by the "".
>
> Yes, that was my first assumption. Look at the name of the directory:
> it's the source tree. And GNU find works fine. I did this on
> numerous directories.
>
> OK, if nobody else has seen it, I'll follow it up and see what the
> problem really is. Watch this space.
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.
Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970926171729.56024>