All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: Autofs weirdness in nsswitch.conf and other stuff...
Date: Fri, 16 Mar 2007 14:21:23 -0400	[thread overview]
Message-ID: <45FAE023.5010805@redhat.com> (raw)
In-Reply-To: <1174066773.3397.76.camel@raven.themaw.net>

Ian Kent wrote:
> On Fri, 2007-03-16 at 10:09 -0700, Jim Carter wrote:
>   
>> On Sat, 17 Mar 2007, Ian Kent wrote:
>>
>>     
>>> Let me see if I can clear this up.
>>> ...
>>> The first instance of a master map that is found, using nsswitch, is
>>> used unless it is explicitly specified, such as "/etc/auto.master",
>>> ...
>>> The first instance of each autofs managed indirect mount that is found
>>> in the master map is used. The corresponding map given in the entry is
>>> looked for by using nsswitch specified sources unless the source is
>>> explicitly given, such as "/etc/auto.mymap" in which case only that map
>>> is used. Additional instances of the same indirect mount point in the
>>> configuration are ignored.
>>> ...
>>> Automount key lookups use the same rules as the lookup of maps above and
>>> the first instance of a map key found is used.
>>>       
>> Yes, this does clear it up.  Autofs' philosophy differs from other 
>> nsswitchable maps, where a key is looked for in potentially every listed 
>> data source until found.  Whereas, autofs identifies the first map that 
>> exists, and looks up a key in that map, and if it's absent, you lose.  It 
>> doesn't go on to look for the key in subsequent data sources such as LDAP, 
>> unless the plus kludge has been used.  (In any case, the first found 
>> instance of the key is used and subsequent instances or sources are 
>> not looked at.)
>>     
>
> Maybe I have got this wrong then.
>
> I thought the default nsswitch action was [NOTFOUND=continue] so autofs
> will search multiple source instances of a given map name for a key and
> the first match will succeed or not found will be returned. This is so
> only if the map source is not explicitly given in the map name in which
> case only that map source will be consulted.

This is how I thought that it was supposed to work as well.

It would seem to be the right way and I suspect, should not prevent us from
using the Connectathon testsuite if we wish.  Even if if does, then we 
should
investigate to see why any failures might occur and either fix the testsuite
or make a better informed decision about the semantics of autofs at that 
time.

    Thanx...

       ps

  reply	other threads:[~2007-03-16 18:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 22:05 Autofs weirdness in nsswitch.conf and other stuff weiler
2007-03-16  1:34 ` Ian Kent
2007-03-16  2:41   ` Erich Weiler
2007-03-16 13:19   ` Peter Staubach
2007-03-16 14:24     ` Ian Kent
2007-03-16 14:37       ` Peter Staubach
2007-03-16 14:56         ` Jeff Moyer
2007-03-16 15:16           ` Erich Weiler
2007-03-16 16:32             ` Ian Kent
2007-03-16 17:09               ` Jim Carter
2007-03-16 17:21                 ` Jeff Moyer
2007-03-16 17:39                 ` Ian Kent
2007-03-16 18:21                   ` Peter Staubach [this message]
2007-03-19  3:35                     ` Ian Kent
2007-03-19 18:14                   ` Jim Carter
2007-03-16 16:25       ` Jim Carter
2007-03-16 16:49         ` Jeff Moyer

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=45FAE023.5010805@redhat.com \
    --to=staubach@redhat.com \
    --cc=autofs@linux.kernel.org \
    --cc=raven@themaw.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.