From owner-freebsd-current Sat Jan 26 12:54:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (w250.z064001178.sjc-ca.dsl.cnc.net [64.1.178.250]) by hub.freebsd.org (Postfix) with SMTP id 3B3CD37B402 for ; Sat, 26 Jan 2002 12:54:30 -0800 (PST) Received: (qmail 41102 invoked by uid 1000); 26 Jan 2002 20:54:51 -0000 Date: Sat, 26 Jan 2002 12:54:29 -0800 From: Jos Backus To: freebsd-current@freebsd.org Subject: Re: Processes hanging in ``inode' state Message-ID: <20020126205451.GA40862@lizzy.bugworks.com> Reply-To: Jos Backus Mail-Followup-To: freebsd-current@freebsd.org References: <20020125235130.GA69092@lizzy.bugworks.com> <20020126024324.A73968@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020126024324.A73968@dragon.nuxi.com> User-Agent: Mutt/1.3.26i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Jan 26, 2002 at 02:43:24AM -0800, David O'Brien wrote: > I have been living with this in -CURRENT since mid-summer. I am lucky to > have 1 week uptimes. Wow. My home system seems to do much better than that and I track -current very closely on both my home and work system. But I'm not using NFS (client or server) at home, maybe that has something to do with it? > What editor are you using? I lock up my system most often using > mutt+vim. Interesting. I have seen it happen with vim twice but not with mutt. But I don't use mutt at work. -- Jos Backus _/ _/_/_/ Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ josb@cncdsl.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message