From: Steve Dickson <SteveD@redhat.com>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] [nfs-utils: mountd] exports too verbose.
Date: Fri, 16 Mar 2007 09:22:26 -0400 [thread overview]
Message-ID: <45FA9A12.1030602@RedHat.com> (raw)
In-Reply-To: <17913.58996.50116.344398@notabene.brown>
Neil Brown wrote:
> On Tuesday March 13, SteveD@redhat.com wrote:
>> This patch is relative to the git tree at:
>> git://git.infradead.org/~steved/nfs-utils.git
>> which has been updated to the nfs-utils-1.0.12
>> release.
>>
>> Please consider...
>
> How about this instead...
> nfs-utils imposes an ordering to some extent. hostnames first, then
> subnets, the wildcards, then netgroups.
> If the two names are in different places in that ordering, then there
> really is no need to report anything, as in you case.
>
> OK?
>
> NeilBrown
>
> diff --git a/utils/mountd/cache.c b/utils/mountd/cache.c
> index 6cf24ce..ed7fe35 100644
> --- a/utils/mountd/cache.c
> +++ b/utils/mountd/cache.c
> @@ -490,6 +490,7 @@ void nfsd_export(FILE *f)
> int i;
> char *dom, *path;
> nfs_export *exp, *found = NULL;
> + int found_type = 0;
>
>
> if (readline(fileno(f), &lbuf, &lbuflen) != 1)
> @@ -516,9 +517,10 @@ void nfsd_export(FILE *f)
> continue;
> if (strcmp(path, exp->m_export.e_path))
> continue;
> - if (!found)
> + if (!found) {
> found = exp;
> - else {
> + found_type = i;
> + } else if (found_type == i) {
> xlog(L_WARNING, "%s exported to both %s and %s in %s",
> path, exp->m_client->m_hostname, found->m_client->m_hostname,
> dom);
hmm... isn't there still a possibility that every time
the mis-orders exported is accessed, the a message will
be logged? So it might make sense to only log this
message once, right?
Also since this is a reordering problem, shouldn't the
logged message say its a re-ordering problem, so
people will know how to fix it? At this point, the
message is stating the obvious... which is really
not that helpful as to how to avoid the message... imho..
steved.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-16 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 16:02 [PATCH] [nfs-utils: mountd] exports too verbose Steve Dickson
2007-03-16 0:36 ` Neil Brown
2007-03-16 13:22 ` Steve Dickson [this message]
2007-03-18 23:23 ` Neil Brown
2007-03-19 18:47 ` Steve Dickson
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=45FA9A12.1030602@RedHat.com \
--to=steved@redhat.com \
--cc=neilb@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.