From: Richard Miller <9fans@hamnavoe.com>
To: mtg@crn.mteege.de, 9fans@cse.psu.edu
Subject: Re: [9fans] nfsserver no mapping
Date: Mon, 31 Jan 2005 15:52:54 +0000 [thread overview]
Message-ID: <d26215f04bf795e3bf0f5ad4dccda362@hamnavoe.com> (raw)
In-Reply-To: <a5139a9c80464e90980d6cad5303c2f1@crn.mteege.de>
>> you try '9fs crn' on crn?
>
> it mounts crn to /n/crn and I can see the tree.
Try '-D' flag for more detailed status messages. If you are still
seeing the "no map for pair" message, it may be that the client
IP is mapping to a name which doesn't match the client regexp
in the configuration file.
-- Richard
next prev parent reply other threads:[~2005-01-31 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fbcfa173833558cd93d5a581cdf62e94@hamnavoe.com>
2005-01-31 14:50 ` Matthias Teege
2005-01-31 15:52 ` Richard Miller [this message]
[not found] <01db1b7d580db9b1364b20b1cc200ac5@hamnavoe.com>
2005-01-31 13:06 ` Matthias Teege
2005-01-31 14:19 ` Richard Miller
2005-01-31 7:29 Matthias Teege
2005-01-31 9:47 ` Richard Miller
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=d26215f04bf795e3bf0f5ad4dccda362@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@cse.psu.edu \
--cc=mtg@crn.mteege.de \
/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;
as well as URLs for NNTP newsgroup(s).