From: Alexander Reeder Subject: exports(5) formatting question Date: Thu, 16 May 2002 07:55:14 -0500 Sender: nfs-admin@lists.sourceforge.net Message-ID: <20020516125514.GA3280@ns.e-sa.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: To: nfs@sourceforge.net Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: There seems to be a problem in the behavior of exports(5) evaluation of /etc/exports. For example, how would I write an /etc/exports file to export a file system to 172.16.x.x read-only, with an exception of read-write to 172.16.4.1? The following would seemingly be the answer: /export 172.16.0.0/16(ro) 172.16.4.1(rw) But after server reboot, the client 172.16.4.1 can't write to NFS. Sorry but I've not yet looked at it in detail. On Solaris I can write an equivalent request like this: share -F nfs -o ro=-172.16.4.1:@172.16.0.0/16 ,rw=172.16.4.1 /export On a similar, but different note, it'd be nice to allow the following expression: /home 172.16.0.0/16(rw) /home/jondoe 172.16.0.0/16(ro) Solaris displays an error message (parent-directory (/home) already shared) and cannot do this; *BSD's NFS server is per-filesystem-basis and allow this only if /home/jondoe is on a different filesystem. _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs