Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: funny bug
- To: tlug@example.com
- Subject: Re: funny bug
- From: Austin Kurahone <austin@example.com>
- Date: Fri, 30 Mar 2001 14:58:09 +0900
- Content-Disposition: inline
- Content-Type: multipart/signed; micalg=pgp-md5;protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW"
- In-Reply-To: <3AC417F8.41194.001@example.com>; from vp@example.com on Fri, Mar 30, 2001 at 02:22:00PM +0900
- References: <3AC417F8.41194.001@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <LIRKXC.A.AnC.xCCx6@example.com>
- Resent-Sender: tlug-request@example.com
- User-Agent: Mutt/1.2.5i
On Fri, Mar 30, 2001 at 02:22:00PM +0900, Viktor Pavlenko wrote: > >Thanks for sharing the bug. Not knowing much about shell > >scripting I was wondering if you could explain the bug? > >It's a bit too subtle for me ;) > > Shell expands [pP]rog_name to progname if progname is in the > current directory and grep process name becomes `grep progname'. > So `ps -ef | grep progname' will show the grep process too. > > And `ps -ef | grep '[pP]rogname'' will not. I suppose that's simpler than adding "| grep -v grep". -- Austin K. Kurahone Tokyo Linux Users Group / SIGUSR1 R&D Hail Eris! All Hail Discordia! "One must still have chaos in one to give birth to a dancing star!" --Nietzshe
- References:
- Re: funny bug
- From: vp@example.com (Viktor Pavlenko)
Home | Main Index | Thread Index
- Prev by Date: Re: funny bug
- Next by Date: Re: funny bug
- Prev by thread: Re: funny bug
- Next by thread: Re: funny bug
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links