From owner-freebsd-current Fri Dec 22 23:56:57 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 22 23:56:55 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E1BF037B400; Fri, 22 Dec 2000 23:56:54 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id XAA25014; Fri, 22 Dec 2000 23:57:03 -0800 Date: Fri, 22 Dec 2000 23:56:54 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Assar Westerlund Cc: current@FreeBSD.ORG Subject: Re: is it possible to have a NULL procp for an NFS request? In-Reply-To: <5lu27vlgz0.fsf@assaris.sics.se> 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 I'm pretty sure that the server had no symlinks in that filesystem. On 23 Dec 2000, Assar Westerlund wrote: > Matthew Jacob writes: > > Hmm. The client wasn't following symlinks. > > You sure? What happens is when you queue up an nfs operation provoked > by following a symlink. I couldn't figure any other way of making > that happen. > > > The patch seems simple enough, but it probably shouldn't just > > swallow the error. > > Yeah, your patch to subr_prf.c is better. Well, it covers more. Sigh. Just pluggin' holes.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message