All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Bon <stef@bononline.nl>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: include a master file: where does the automounter look
Date: Mon, 28 Apr 2008 11:12:11 +0200	[thread overview]
Message-ID: <481594EB.3020703@bononline.nl> (raw)
In-Reply-To: <1209373447.3243.34.camel@raven.themaw.net>

Ian Kent wrote:
> On Mon, 2008-04-28 at 16:53 +0800, Ian Kent wrote:
>   
>> On Mon, 2008-04-28 at 10:32 +0200, Stef Bon wrote:
>>     
>>> Hello,
>>>
>>> when I read the manpage for auto.master (and other docs) I see that I 
>>> can include another master file by doing:
>>>
>>> +auto.master
>>>
>>> The comment says that by doing so, the you can specify a master map 
>>> which is found using
>>> nsswitch sources.
>>> What happens then? Where does it look then?
>>>       
>> If you have a line in /etc/nsswitch.conf like:
>>
>> automount: files nis
>>
>> it will look in /etc for auto.master (files) and try to connect to a nis
>> server and ask for auto.master.
>>     
>
> There's actually a bit more to it than that because of the possibility
> of different actions, such as continuing or returning when a source is
> found or not.
>   
Thanks a lot for the info.

Stef Bon

BTW I'm working on documentating the construction I'm using right now. 
It's not ready, but when I'm happy, I will also
redo the already existing documentation on howtoforge.

Look at:

http://linux.bononline.nl/linux/automountsmbshares/automountsmbshares-page01a.php

  reply	other threads:[~2008-04-28  9:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28  8:32 include a master file: where does the automounter look Stef Bon
2008-04-28  8:53 ` Ian Kent
2008-04-28  9:04   ` Ian Kent
2008-04-28  9:12     ` Stef Bon [this message]
2008-04-28  9:25       ` Ian Kent
2008-04-28 14:27   ` Stef Bon
2008-04-28 14:39     ` 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=481594EB.3020703@bononline.nl \
    --to=stef@bononline.nl \
    --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.