linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Leopold <matthias@aic.at>
To: linux-nfs@vger.kernel.org
Subject: multiple mounts of same share on one host?
Date: Fri, 25 Apr 2014 12:11:43 +0200	[thread overview]
Message-ID: <535A34DF.5010302@aic.at> (raw)

hi,

i've got a (probably rather basic) nfs usage question. i hope this is 
the right place to ask, please tell me otherwise.

i'm moving webspace content to nfs shares. because of suexec 
restrictions i have different paths to different subsets of the content 
on the client, but i wonder if i can still have all of the content in 
one path on one exported nfs share.

example:

i need

/home/content/foo

and

/var/www/content/bar

exported share "/export" could have

/export/foo
/export/bar

AFAICS there are three options:

.) mounting /export twice on different paths on the nfs client
.) mounting /export once and doing a bind mount
.) put foo and bar in different directories and exporting/mounting them 
separately

which of these options would you recommend?

thx very much for help
matthias



                 reply	other threads:[~2014-04-25 10:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=535A34DF.5010302@aic.at \
    --to=matthias@aic.at \
    --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;
as well as URLs for NNTP newsgroup(s).