Linux NFS development
 help / color / mirror / Atom feed
From: Tom McNeal <trmcneal@attbi.com>
To: Peter Staubach <Peter.Staubach@Sun.COM>,
	NFS maillist <nfs@lists.sourceforge.net>
Subject: Re: [Fwd: take away nfs write permissions instantly]
Date: Thu, 20 Jun 2002 11:11:09 -0700	[thread overview]
Message-ID: <3D121ABD.F14144F8@attbi.com> (raw)
In-Reply-To: 200206201741.g5KHfY121536@amunet.Central.Sun.COM

Hi -

Here is an update on Solaris behavior from a SUN architect; 
I hadn't realized it would notice the export change and 
return errors.  I'd assume that Linux is behaving like I 
said, but it appears that it should notice.  

Tom


Peter Staubach wrote:
> 
> 
> Re-exporting a file system to remove write permission will immediately
> disable all clients from writing through that export.  The client will
> not know that the files are now read-only, but they will be.  The file
> system does not need to be remounted or anything else like that.  The
> EROFS errors will just start being returned from the server to the
> client.
> 
> When this person indicates that the client could still write data,
> I would presume that the write(2) system call appears to succeed,
> ie. doesn't return an error, but encounters the EROFS error later
> when it actually tries to write the data to the server.
> 
>                 ps

--
------------------------------------------------------------
Tom McNeal       trmcneal@attbi.com     (650)906-0761 (cell) 
------------------------------------------------------------


-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

           reply	other threads:[~2002-06-20 18:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200206201741.g5KHfY121536@amunet.Central.Sun.COM>]

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=3D121ABD.F14144F8@attbi.com \
    --to=trmcneal@attbi.com \
    --cc=Peter.Staubach@Sun.COM \
    --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