From owner-freebsd-current Thu Sep 21 03:32:36 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA02699 for current-outgoing; Thu, 21 Sep 1995 03:32:36 -0700 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA02692 for ; Thu, 21 Sep 1995 03:32:27 -0700 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id LAA22070; Thu, 21 Sep 1995 11:34:27 +0100 Date: Thu, 21 Sep 1995 11:34:25 +0100 (BST) From: Doug Rabson To: Bruce Evans cc: current@freebsd.org Subject: Re: pathconf under nfsv3 In-Reply-To: <199509201209.WAA25816@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Wed, 20 Sep 1995, Bruce Evans wrote: > How is pathconf() supposed to work under nfsv3? The server seems to > support it, but the client just returns EINVAL without asking the > server. It looks like Rick wrote the server side without filling in the client side. Someone needs to fill in the client side with suitable code to make the rpc. Is it worth faking the information for NFSv2? -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939