From: seth vidal <skvidal@phy.duke.edu>
To: Dave Ingram <davei@wolfram.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: recursive NFS export of mounted ISO images
Date: 23 Oct 2002 16:19:32 -0400 [thread overview]
Message-ID: <1035404373.31676.36.camel@opus> (raw)
In-Reply-To: <Pine.LNX.4.44.0210231512570.31286-100000@wopr.wolfram.com>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
On Wed, 2002-10-23 at 16:16, Dave Ingram wrote:
> On 23 Oct 2002, seth vidal wrote:
>
> > You might be able to work some dark magic with autofs over the nfs
> > exported locations.
> >
> > look into how autofs functions - I think it might just be possible if
> > you're not afraid of some painful thinking.
>
> :) I wrestled with this on the 2nd night of trying to come up with
> a solution.
>
> While this may simplify the client's transaction, the server now
> has to automatically:
>
> 1. Create an auto.XXX autofs config file for every ISO mounted directory
> 2. Update /etc/auto.master
> 3. the autofs daemon gets reloaded for each new addition/subtraction
>
> All of this needs to be done by root as well. Of course, a
> specialized SUID wrapper can be constructed to do this, but it's still a
> bit of a boondoggle. It's fair to say, however, that almost any solution
> currently will have to be a bit of a hack.
>
> But it's hard to believe that there aren't other people with a
> genuine need for something like this sort of dynamic recursive
> distribution.
>
> Thanks very much for the fast response!
You could do it via nis maps - then no restarting the autofs daemon at
all.
Additionally, you could have the maps dynamically generated and pushed
from the nis master.
one place, less pain.
-sv
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-10-23 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 19:51 recursive NFS export of mounted ISO images Dave Ingram
2002-10-23 20:07 ` seth vidal
2002-10-23 20:16 ` Dave Ingram
2002-10-23 20:19 ` seth vidal [this message]
2002-10-23 20:07 ` David B. Ritch
2002-10-23 20:17 ` recursive NFS export of mounted ISO images -- Automounter Maps? Bryan J. Smith
2002-10-23 20:29 ` Dave Ingram
2002-10-23 20:44 ` Bryan J. Smith
2002-10-23 20:55 ` Dave Ingram
2002-10-23 21:18 ` Bryan J. Smith
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=1035404373.31676.36.camel@opus \
--to=skvidal@phy.duke.edu \
--cc=davei@wolfram.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