From owner-freebsd-hackers Tue Nov 16 10: 3:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id EB76515239 for ; Tue, 16 Nov 1999 10:03:09 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id KAA02088; Tue, 16 Nov 1999 10:03:07 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 16 Nov 1999 10:03:07 -0800 (PST) From: Doug White To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS In-Reply-To: <199911160329.WAA92082@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Nov 1999, David E. Cross wrote: > I am noticing a large number of pine (and only pine) procs stuck in disk-wait. > All of the are in the WCHAN "vmpfw". Any ideas what this may mean? Is the mail spool pine accessing on this NFS volume, or just the binary? If so you're breaking the cardinal rule of NFS: Never serve mail spools via NFS. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message