Linux NFS development
 help / color / mirror / Atom feed
From: Kapeller Rene PSI <rene.kapeller@psi.ch>
To: nfs@lists.sourceforge.net
Subject: take away nfs write permissions instantly
Date: Thu, 20 Jun 2002 12:39:59 +0200	[thread overview]
Message-ID: <3D11B0FF.8030008@psi.ch> (raw)

Can anyone help me on the following problem:

In order to take away nfs write permissions instantly for a previously 
mounted
nfs directory called '/data', I'm changing the export options for '/data'
on the server to 'ro', while keeping the mount on the client.

exportfs -io ro,sync,wdelay,no_root_squash nfsclient:/data

exportfs -v
/data   nfsserver(ro,wdelay,no_root_squash)

Surprisingly the client can still write to /data at this point, unless I do
umount/mount of /data.

Is this the way it's suposed to work?

Changing the nfs export options on a  SunOS 5.6 while clients have mounted
a nfs path, write permissions are instantly taken away from it.

share -F nfs -o ro,root=nfsclient /data

In both cases I used the following nfs mount options:
mount -o rw,sync,nfsvers=3,wsize=32768,rsize=32768

Thanks!
- Rene




-------------------------------------------------------
                   Bringing you mounds of caffeinated joy
                   >>>     http://thinkgeek.com/sf    <<<

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2002-06-20 10:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20 10:39 Kapeller Rene PSI [this message]
2002-06-20 14:24 ` take away nfs write permissions instantly Stuart Sheldon
2002-06-20 14:58   ` Kapeller Rene PSI
2002-06-20 16:44     ` Tom McNeal
2002-06-21  3:00 ` Neil Brown
2002-06-21  3:47   ` Kapeller Rene PSI
2002-06-21  5:13     ` Neil Brown
2002-06-21 14:57       ` Bernd Schubert
2002-06-21 18:04         ` Tom McNeal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D11B0FF.8030008@psi.ch \
    --to=rene.kapeller@psi.ch \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox