Linux NFS development
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: nfs@lists.sourceforge.net
Subject: overlapping/conflicting entries in /proc/net/rpc/nfsd.export/content
Date: Tue, 29 Nov 2005 09:10:40 -0500	[thread overview]
Message-ID: <1133273443.25136.66.camel@pc.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 600 bytes --]

I have what seem to be overlapping/conflicting entries
in /proc/net/rpc/nfsd.export/content.  The two entries that seem to
conflict each other are:

/home   10.75.22.0/24,pc.ilinx(rw,no_root_squash,sync,wdelay)
/home   pc.ilinx(rw,no_root_squash,sync,wdelay)

I believe these are the cause of the following messages littering my
syslog:

12:53:27 rpc.mountd /home exported to both 10.75.22.0/24 and pc.ilinx in 10.75.22.0/24,pc.ilinx

How do I clean up that /proc/net/rpc/nfsd.export/content?

Thanx,
b.

-- 
My other computer is your Microsoft Windows server.

Brian J. Murrell

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2005-11-29 14:10 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=1133273443.25136.66.camel@pc.local \
    --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