From: "H. J. Lu" <hjl@lucon.org>
To: Mark Goodwin <markgw@sgi.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: empty /etc/exports causes nfs rc script to exit
Date: Mon, 3 Feb 2003 10:02:07 -0800 [thread overview]
Message-ID: <20030203100207.A12532@lucon.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0302031125590.16330-100000@sherman.melbourne.sgi.com>; from markgw@sgi.com on Mon, Feb 03, 2003 at 11:31:21AM +1100
On Mon, Feb 03, 2003 at 11:31:21AM +1100, Mark Goodwin wrote:
>
> Is there some good reason why the nfs rc script exits if /etc/exports
> is empty? [ -s /etc/exports ] || exit 0
>
> If an admin adds something to /etc/exports, they have to kick the
> rc script too. Seems silly.
>
We did
# echo "#" > /etc/exports
for this purpose.
H.J.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-02-03 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 0:31 empty /etc/exports causes nfs rc script to exit Mark Goodwin
2003-02-03 1:10 ` Neil Brown
2003-02-03 18:02 ` H. J. Lu [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=20030203100207.A12532@lucon.org \
--to=hjl@lucon.org \
--cc=markgw@sgi.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