Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site calma.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!sun!calma!radzy
From: radzy@calma.UUCP (Tim Radzykewycz)
Newsgroups: net.bugs.4bsd
Subject: Re: slight problem with grep.
Message-ID: <140@calma.UUCP>
Date: Mon, 3-Feb-86 15:11:01 EST
Article-I.D.: calma.140
Posted: Mon Feb  3 15:11:01 1986
Date-Received: Wed, 5-Feb-86 01:32:01 EST
References: <9299@ritcv.UUCP>
Reply-To: radzy@calma.UUCP (Tim Radzykewycz)
Distribution: net
Organization: GE/Calma Co., R&D Systems Engineering, Milpitas, CA
Lines: 19
Keywords: grep

In article <9299@ritcv.UUCP> jxs7451@ritcv.UUCP () writes:
>What happened is I used grep like this to find all of them.
>
>	grep write * > zzzz
>
>having zzzz being a random file.

Note that this will only happen if 'zzzz' is an existing file.  If
either of the following situations occur, there won't be a problem:
	grep write * > AAAA		<- AAAA doesn't contain 'write'
	rm zzzz ; grep write * > zzzz

In the first situation, the file 'AAAA' is searched first.
In the second situation, the '*' doesn't match the file 'zzzz',
so grep never even opens it.
-- 
Tim (radzy) Radzykewycz, The Incredible Radical Cabbage.
	calma!radzy@ucbvax.ARPA
	{ucbvax,sun,csd-gould}!calma!radzy