Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeremy Sanders
	<jeremy-rZTbbJwr4dtS98Db7trcLl6hYfS7NtTn@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: FAQ: Updating shared executables
Date: Tue, 9 Dec 2008 17:44:45 -0500	[thread overview]
Message-ID: <20081209224445.GA12335@fieldses.org> (raw)
In-Reply-To: <ghm8pm$d6c$1@ger.gmane.org>

On Tue, Dec 09, 2008 at 05:10:14PM +0000, Jeremy Sanders wrote:
> Hi - I notice the FAQ says that the crashes caused by updating shared
> libraries on NFS partitions are due to cash consistency rules (FAQ D9).
> Does NFSv4 fix this issue?

No, you still need the workaround described there:

	http://nfs.sourceforge.net/#faq_d9

	"The correct way to update executables and shared libraries on
	your NFS shares is to use the install program with the '-b'
	option. That renames the version of the executable that is in
	use, then creates a brand new file to contain the new version of
	the executable."

--b.

      reply	other threads:[~2008-12-09 22:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09 17:10 FAQ: Updating shared executables Jeremy Sanders
2008-12-09 22:44 ` J. Bruce Fields [this message]

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=20081209224445.GA12335@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jeremy-rZTbbJwr4dtS98Db7trcLl6hYfS7NtTn@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    /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