bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bugreport grep (GNU grep) 2.4.2


From: Bob Proulx
Subject: Re: bugreport grep (GNU grep) 2.4.2
Date: Mon, 4 May 2009 08:28:53 -0600
User-agent: Mutt/1.5.18 (2008-05-17)

Blaauboer, Dick wrote:
> Now I type grep Hello *.LOG>output.LOG (return)
> The program goes into a loop. It seems to see the outputfile (also a
> .LOG) as one of the files it has to check, adding its findings over and
> over again.

Yes.  That is exactly correct.  The "*.LOG" matches the file
"output.LOG" and therefore includes the output file in the list of
input files.  It has done exactly what you told it to do.

> Ctrl C did stop this loop but the result was a file of about 64 Mb, text
> only.

Sure.

> At home I will try to see what happens when I do not interrupt the
> program.  Must crash somewhere, disk full (?) of file too big (?) or
> something like that.

Eventually the disk for the output file will be consumed and will
return a write error.

> Not a big bug. Just don't name the outpufile .LOG

Agreed.  Alternatively you can specify the list of input files not
using a wildcard and therefore also avoid listing the output file with
the input files.

> Hope I have helped you with this "bug-report".

But you didn't report any bugs.  There is no bug there.  You even
described the behavior correctly.  Therefore I am very confused by
your statement.  What did you think was a bug?

Bob




reply via email to

[Prev in Thread] Current Thread [Next in Thread]