From owner-freebsd-questions@FreeBSD.ORG Sun Feb 27 17:21:17 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F5F516A4CE for ; Sun, 27 Feb 2005 17:21:17 +0000 (GMT) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id B305043D2D for ; Sun, 27 Feb 2005 17:21:07 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id j1RHL1qS003509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 27 Feb 2005 09:21:02 -0800 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.10/Submit) id j1RHL1FL003507 for freebsd-questions@freebsd.org; Sun, 27 Feb 2005 09:21:01 -0800 X-Authentication-Warning: hosea.tallye.com: sttng359 set sender to lorenl@alzatex.com using -f Date: Sun, 27 Feb 2005 09:21:01 -0800 From: "Loren M. Lang" To: f-q Message-ID: <20050227172101.GB1672@alzatex.com> References: <003801c51b2b$1deecc60$04cf589d@simula.eis.uva.es> <20050225135707.GC18789@alzatex.com> <20050226044248.GA2467@holestein.holy.cow> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050226044248.GA2467@holestein.holy.cow> User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C Subject: Re: I killed my system with grep X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 17:21:17 -0000 On Fri, Feb 25, 2005 at 11:42:48PM -0500, Parv wrote: > in message <20050225135707.GC18789@alzatex.com>, > wrote Loren M. Lang thusly... > > > > On Fri, Feb 25, 2005 at 12:14:04PM +0100, Ramiro Aceves wrote: > > > > > > I am running a FreeBSD 5.3 system with 64MB RAM and 150 MB swap. > > > > > > Yesterday I entered the command: > > > > > > # grep -R something / > > > > You probably hit a file under /dev/ and caused grep to hang. It's > > possible that as root, certain device files might hang the system, > > but nothing comes to mind at the moment unless /dev/io could do > > it. Also, think about what happens when grep hit's /dev/zero. It > > will never finish. > > Would using -I option (not search text-like files) help to avoid > above described hang ups in /dev? No, it still searches all files, it just doesn't print the usual line that it matched, only whether there was success or not. You really just need to make sure grep never goes into /dev. Since your running 5.x, /dev is it's own filesystem of a unique type, so the following command will run grep on only filesystems of type ufs, which won't include network filesystems, or /dev: find / -fstype ufs -exec grep -H something {} \; > > > - Parv > > -- -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C