All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: autofs mailing list <autofs@linux.kernel.org>
Subject: Re: [autofs4 patch] implement included map support
Date: Thu, 09 Nov 2006 13:20:40 +0800	[thread overview]
Message-ID: <1163049640.7831.3.camel@localhost> (raw)
In-Reply-To: <x491wodnvdk.fsf@segfault.boston.devel.redhat.com>

On Wed, 2006-11-08 at 22:37 -0500, Jeff Moyer wrote:
> Hi, Ian, list,  (again, sorry if this is a dup)
> 
> Here is an implementation of included map support for autofs v4.  This
> supports included maps in both the master map, and regular direct or
> indirect file maps.
> 
> Because I dread writing bash code, I implemented the included map
> checking for the master map in C.  We basically just call into the
> daemon with a bogus mount point, asking for it to dump out all of the
> maps.  This works well for 2 reasons: 1) it's not bash, and 2) it
> re-uses the code that the daemon will use to read the included maps
> anyway.
> 
> Review would be greatly appreciated.  I tested this in my environment
> by creating a number of included maps, and modifying
> /etc/nsswitch.conf to ensure that it works as expected for file and
> NIS maps.

I've only looked briefly at this but I get the impression that it will
allow "+" map inclusion from other than file maps. Is that right?

If that is the case we need to explicitly ignore "+" map entries in map
sources other than file maps as it's not legal or at least for
consistency.

Ian

  reply	other threads:[~2006-11-09  5:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09  3:37 [autofs4 patch] implement included map support Jeff Moyer
2006-11-09  5:20 ` Ian Kent [this message]
2006-11-09 15:09   ` Jeff Moyer
2006-11-10  4:02     ` 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=1163049640.7831.3.camel@localhost \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=jmoyer@redhat.com \
    /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.