linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: nfs@lists.sourceforge.net, neilb@redhat.com, trond.myklebust@fys.uio.no
Cc: Stephen Tweedie <sct@redhat.com>, linux-fsdevel@vger.kernel.org
Subject: Re: Wildcards matching ".": exports bug or just documentation bug?
Date: Wed, 13 Nov 2002 13:55:22 +0000	[thread overview]
Message-ID: <20021113135522.B3115@redhat.com> (raw)
In-Reply-To: <20021004125704.A8969@redhat.com>; from sct@redhat.com on Fri, Oct 04, 2002 at 12:57:04PM +0100

Hi,

On Fri, Oct 04, 2002 at 12:57:04PM +0100, Stephen C. Tweedie wrote:
 
> mountd treats wildcards in hostnames in the exports file as matching
> anything, including ".".
> However, the exports man page explicitly states that "*" and "?" do not
> match ".":
 
> So, which is right, the actual behaviour or the documented behaviour?
> I'd tend to lean towards the former.

Ping?  This is a pretty serious discrepancy between the documented and
implemented behaviour.  The documentation *explicitly* states that

	*.com

won't match foo.bar.com, but the implentation matches this just fine.
Given that the documented behaviour doesn't actually give you a way to
match an export for all arbitrarily-deep subdomains underneath a
domain, I'd think matching subdomains of all levels with "*" makes
more sense than matching only a single level, so it's the
documentation that needs to be updated.

--Stephen

  reply	other threads:[~2002-11-13 13:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 11:57 Wildcards matching ".": exports bug or just documentation bug? Stephen C. Tweedie
2002-11-13 13:55 ` Stephen C. Tweedie [this message]
2002-11-13 22:13   ` 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=20021113135522.B3115@redhat.com \
    --to=sct@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=neilb@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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).