Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!amdcad!lll-crg!seismo!rochester!ritcv!jxs7451
From: jxs7451@ritcv.UUCP (Jeffrey Smith)
Newsgroups: net.bugs.4bsd
Subject: slight problem with grep.
Message-ID: <9299@ritcv.UUCP>
Date: Thu, 30-Jan-86 18:55:52 EST
Article-I.D.: ritcv.9299
Posted: Thu Jan 30 18:55:52 1986
Date-Received: Sat, 1-Feb-86 21:31:10 EST
Reply-To: jxs7451@ritcv.UUCP ()
Distribution: net
Organization: Rochester Institute of Technology, Rochester, NY
Lines: 20
Keywords: grep


Just wanted to mention a slight problem with the UNIX grep command.
What happens actually makes sence, but it does tend to be annoying
if you are caught by it.

Anyway, say you are in a directory that contains some Pascal source
code.  Now this is what happened to me.  I wanted to find all of the
write statements in my programs that i had used for debugging.
What happened is a used grep like this to find all of them.

	grep write * > zzzz

having zzzz being a random file.  I used at to run this in the batchmode
and i came back and got a quota exceeded message.  What happens is
grep searches for write in zzzz after it has already written all of
the previouly founded writes to this file.  Needless to say that this
is not a good situation.

Jeffrey Smith    JMS7451@RITVAXC.BITNET
	         jxs7451!ritcv