From owner-freebsd-current Wed Oct 14 09:55:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20117 for freebsd-current-outgoing; Wed, 14 Oct 1998 09:55:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20068 for ; Wed, 14 Oct 1998 09:55:11 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id MAA01502; Wed, 14 Oct 1998 12:56:32 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Wed, 14 Oct 1998 12:56:32 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: -current NFS problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Oct 1998, Brian Feldman wrote: > Perhaps this could be the problem with NFS "hanging" certain people all > the time? (not the pine thing) The system spending way too much time > inside the kernel transmitting NFS packets.... > > Brian Feldman > The way I understand it, unless you aren't running nfsiod processes this shouldn't be an issue, all NFS requests except close are done async and passed off to the nfsiod's to handle for the client. btw, my pine problem *might* have somehow gone with my last kernel build, I'm not sure though. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message