From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: nfs@lists.sourceforge.net
Subject: funniness going on with exports
Date: Wed, 27 Jul 2005 07:59:51 -0400 [thread overview]
Message-ID: <1122465593.7532.12.camel@pc.ilinx> (raw)
[-- Attachment #1: Type: text/plain, Size: 1563 bytes --]
Hi have some funniness going on with doing exports with nfs-utils-1.0.7.
Here is my current exports list:
# cat /proc/fs/nfsd/exports
# Version 1.1
# Path Client(Flags) # IPs
/mnt/data 10.75.22.0/24,pc.ilinx(rw,root_squash,sync,wdelay)
/mnt/mandrake 10.75.22.0/24,pc.ilinx(rw,no_root_squash,sync,wdelay)
/usr/local 10.75.22.0/24,pc.ilinx(rw,no_root_squash,sync,wdelay)
/usr/src 10.75.22.0/24,pc.ilinx(rw,no_root_squash,sync,wdelay)
/mnt/data/mp3 10.75.22.0/24,pc.ilinx(rw,root_squash,sync,wdelay)
/home 10.75.22.0/24,pc.ilinx(rw,no_root_squash,sync,wdelay)
If I add this line to /etc/exports
/mnt/data/photos 10.75.22.0/24(ro,sync)
and then exportfs -r, my exports list looks like this:
# cat /proc/fs/nfsd/exports
# Version 1.1
# Path Client(Flags) # IPs
/mnt/data/photos 10.75.22.0/24,pc.ilinx(ro,root_squash,sync,wdelay)
/mnt/data 10.75.22.0/24,pc.ilinx(rw,root_squash,sync,wdelay)
/mnt/mandrake 10.75.22.0/24,pc.ilinx(rw,no_root_squash,sync,wdelay)
/usr/local 10.75.22.0/24,pc.ilinx(rw,no_root_squash,sync,wdelay)
/usr/src 10.75.22.0/24,pc.ilinx(rw,no_root_squash,sync,wdelay)
/mnt/data/mp3 10.75.22.0/24,pc.ilinx(rw,root_squash,sync,wdelay)
/home 10.75.22.0/24,pc.ilinx(rw,no_root_squash,sync,wdelay)
The new export is taking effect, but even though I only added it with
one IP list/option set, it's being exported with an additional ip/option
set (pc.ilinx(ro,root_squash,sync,wdelay)) to the one I specified in
the /etc/exports list.
Any idea why?
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-07-27 12:00 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=1122465593.7532.12.camel@pc.ilinx \
--to=brian@interlinx.bc.ca \
--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