From owner-freebsd-current  Fri Dec 22 23:44:27 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec 22 23:44:25 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from assaris.sics.se (h122n4fls32o892.telia.com [213.64.47.122])
	by hub.freebsd.org (Postfix) with ESMTP id BF9E437B400
	for <current@FreeBSD.ORG>; Fri, 22 Dec 2000 23:44:24 -0800 (PST)
Received: (from assar@localhost)
	by assaris.sics.se (8.9.3/8.9.3) id IAA04670;
	Sat, 23 Dec 2000 08:44:20 +0100 (CET)
	(envelope-from assar)
Sender: assar@assaris.sics.se
To: mjacob@feral.com
Cc: current@FreeBSD.ORG
Subject: Re: is it possible to have a NULL procp for an NFS request?
References: <Pine.BSF.4.21.0012222323430.74029-100000@beppo.feral.com>
From: Assar Westerlund <assar@FreeBSD.ORG>
Date: 23 Dec 2000 08:44:19 +0100
In-Reply-To: Matthew Jacob's message of "Fri, 22 Dec 2000 23:30:45 -0800 (PST)"
Message-ID: <5lu27vlgz0.fsf@assaris.sics.se>
Lines: 13
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Matthew Jacob <mjacob@feral.com> 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.

/assar


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message