Subject: Re: Grep 2.5.1 bug
From: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
To: djgpp-workers AT delorie DOT com
In-Reply-To: <006501c295e3$05898a90$0100a8c0@p4>
References: <006501c295e3$05898a90$0100a8c0 AT p4>
Content-Type: text/plain
Organization: 
Message-Id: <1038385704.25980.6.camel@leeloo>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.0 
Date: 27 Nov 2002 09:28:24 +0100
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Wed, 2002-11-27 at 08:02, Andrew Cottrell wrote:
> This is an FYI at the moment, unless someone else wants to investigate it.
> 
> I was sent a grep problem by someone, but I cannot read the email address so
> 
> DJGPP_204 C:\dj204\tmp>grep -r "ddd" C:\dj204\tmp\*
> grep: C:\dj204\tmp\RHaaaaaa: Permission denied (EACCES)
> grep: C:\dj204\tmp\RHbaaaaa: Permission denied (EACCES)
> grep: C:\dj204\tmp\cvs: Permission denied (EACCES)

Sounds like directories (especially the 'cvs' one), which suggests that
grep is reading directories (which is the default, though perhaps it
shouldn't be on DOSish systems).
Try adding '-d skip' to ignore dirs; that should shut up the errors.
Also, try using '-d recurse' instead of '-r'; the two are supposed to be
equivalent, but if that also gives the errors, there's clearly a bug in
grep.

> DJGPP_204 C:\dj204\tmp>grep "ddd" ...\*

Is .../blah* supposed to ever match directories? Or just all the files?

Of course, all this assumes the failing names above refer to
directories.

> I will look at this over the next week or two and send another email with my
> results or request for help.

-- 
Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>