All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Valousek <webserv@s3group.cz>
To: "autofs@linux.kernel.org" <autofs@linux.kernel.org>
Subject: Re: Caching negative lookups
Date: Fri, 14 Nov 2008 16:36:38 +0100	[thread overview]
Message-ID: <491D9B06.80605@s3group.cz> (raw)
In-Reply-To: <1226670596.2906.40.camel@zeus.themaw.net>

I do not understand it - I have heard that using indirect maps can cause
unwanted NFS chattering on the network and that negative lookups are
supposed to handle this.
But this chattering I can only imagine when using wildcards like
/home auto.home
with auto.home containing something like:
* nfsserver:/vol/vol0/users/&

This way, if an application check for the existence of say /home/file -
the automounter must ask nfsserver for existence of this file every time
the application asks. But if there are no wildcards in the indirect map
and all valid entries are explicitly listed, no nfs chattering occurs as
autofs knows directly that the mount attempt for  /home/file is invalid
as there is no "file" record in the auto.home map.

Am I right? If yes, that would be a serious argument against using
wildcards in the automount maps.....
Ondrej

  reply	other threads:[~2008-11-14 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 15:03 Caching negative lookups Mike K
2008-11-14  2:08 ` Ian Kent
2008-11-14 13:27   ` Mike K
2008-11-14 13:44     ` Ian Kent
2008-11-14 13:49       ` Ian Kent
2008-11-14 15:36         ` Ondrej Valousek [this message]
2008-11-15 10:25           ` Ian Kent
2008-12-09  6:11 ` Ian Kent
2008-12-09  6:12   ` Ian Kent

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=491D9B06.80605@s3group.cz \
    --to=webserv@s3group.cz \
    --cc=autofs@linux.kernel.org \
    /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.