Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <5.2.0.9.2.20021219143918.03059ee0@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Thu, 19 Dec 2002 14:49:12 -0800 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: Re: Grep says file exists and then doesn't grep it In-Reply-To: <3E023F9C.6060108@fangorn.ca> References: <269620-2200212419214147408 AT M2W097 DOT mail2web DOT com> <269620-2200212419214147408 AT M2W097 DOT mail2web DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Mark, I cannot reproduce your problem, but perhaps it's an interaction with FAT file systems and Windows '98? I have Windows 2K Pro and only one FAT volume, but the command you gave works fine for me on both my NTFS and my FAT volumes. There's also the possibility of this being an issue with your CYGWIN environment variable including "ntea". Do you have sharing enabled on the volume or folder in question? Is the target on an SMB share? If so, is it a Windows server? Samba? Something else? The fact that re-compiling gives you a working version makes me ask if you're trying the same invocation (using the new binary) in the same directory as the failing attempt? Have you done a "CHKDSK /F" (or whatever the Windows '98 equivalent is) lately? Grasping at straws, I know... Randall Schulz At 13:52 2002-12-19, Mark Blackburn wrote: >lhall AT pop DOT ma DOT ultranet DOT com wrote: > >>Works fine here but I'm on W2K. Does 'grep -r -e hello .' or 'grep -r >>hello .' work? > > >No and No. Same result as before. > >Maybe compiling on Win98 makes some sort of difference? I assume it was >originally compiled on W2K. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/