From owner-freebsd-current Thu Apr 12 10:11: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 5B66C37B423 for ; Thu, 12 Apr 2001 10:10:57 -0700 (PDT) (envelope-from mb@imp.ch) Received: from harem (harem.imp.ch [157.161.4.8]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id f3CHAc141506; Thu, 12 Apr 2001 19:10:38 +0200 (CEST) (envelope-from Martin.Blapp@imp.ch) Date: Thu, 12 Apr 2001 19:10:38 +0200 From: Martin Blapp To: Thomas Quinot Cc: current@freebsd.org Subject: Re: NFS export to netgroup with duplicate hosts In-Reply-To: <20010412182900.B30764@cuivre.fr.eu.org> 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 > If we manage it, mountd should soon be able to allow different mount flags > for each path you export in /etc/exports. I'm sorry. But now after some investigations and talks with Robert Watson it seems to be clear that this is not possible due the way nfs works. It would be easy to fix mountd, and to store somewhere the path where the export is tied to, but how should nfsd handle this ? He get's a request for a inode (the namei translation is done on the client side). The server has now to look which flag set belongs the inode. How can he see which set of flags belongs to that inode ? man share_nfs on solaris 7: Unlike previous implementations of share_nfs(1M), access checking for the window=, rw, ro, rw=, and ro= options is done per NFS request, instead of per mount request. In suns implementation of nfs is written (man share) If share commands are invoked multiple times on the same filesystem, the last share invocation supersedes the previous-the options set by the last share command replace the old options. For example, if read-write permission was given to usera on /somefs, then to give read-write permis- sion also to userb on /somefs: That means that it's not possible as I get it. I'll do further investigations to be sure how it works on Solaris exactly. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message