Linux NFS development
 help / color / mirror / Atom feed
From: Greg Banks <gnb@sgi.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: Neil Brown <neilb@suse.de>, nfs@lists.sourceforge.net
Subject: Re: [PATCH] Allow default options in /etc/exports
Date: Wed, 7 Feb 2007 13:28:12 +1100	[thread overview]
Message-ID: <20070207022812.GB27634@sgi.com> (raw)
In-Reply-To: <20070205004844.GA6459@uio.no>

On Mon, Feb 05, 2007 at 01:48:44AM +0100, Steinar H. Gunderson wrote:
> On Mon, Feb 05, 2007 at 11:35:23AM +1100, Neil Brown wrote:
> > I would like to have system-wide defaults too (as you mention).  Any
> > suggestions on syntax?  Having
> > 
> > -sync,no_root_squash,no_subtree_check
> > 
> > would be syntactically consistent (which is good) but is kind-a ugly.
> 
> My first hunch is to put it on the command line (so one could have it in
> /etc/default/nfs-common), but I realize that would be confusing (and possibly
> different across distributions, and less flexible). I'm a bit short on good
> syntax suggestions apart from that, really -- adding a different kind of line
> sounds a bit like opening a can of worms syntax-wise...

How about making the line the exact same syntax as normal
lines but a pseudo export point string which is not a valid
absolute pathname, something like "defaults".  For example:

defaults	*(rw,sync,no_subtree_check)
/foo
/bar		*(insecure)

could mean the same as

/foo		*(rw,sync,no_subtree_check)
/bar		*(rw,sync,no_subtree_check,insecure)

There are export options which cannot usefully appear in such a
defaults line (fsid certainly, perhaps also mountpoint=/somewhere).

Greg.
-- 
Greg (not Dave) Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-02-07  2:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-26 22:58 [PATCH] Allow default options in /etc/exports Steinar H. Gunderson
2007-01-04 14:09 ` Steinar H. Gunderson
2007-02-05  0:35 ` Neil Brown
2007-02-05  0:48   ` Steinar H. Gunderson
2007-02-07  2:28     ` Greg Banks [this message]
2007-02-07  6:30       ` Neil Brown

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=20070207022812.GB27634@sgi.com \
    --to=gnb@sgi.com \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=sgunderson@bigfoot.com \
    /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