From: Ian Kent <raven@themaw.net>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: "autofs@linux.kernel.org" <autofs@linux.kernel.org>
Subject: Re: Automounter to dump maps
Date: Thu, 12 Nov 2009 22:58:01 +0800 [thread overview]
Message-ID: <4AFC2279.6070009@themaw.net> (raw)
In-Reply-To: <x49eio3svsj.fsf@segfault.boston.devel.redhat.com>
Jeff Moyer wrote:
> Ondrej Valousek <webserv@s3group.cz> writes:
>
>> Hi Ian / all,
>>
>> Is there any way to make automounter dump maps it sees? I was just
>> thinking about it - with files / NIS / program backend it is not much
>> needed but it could be quite helpful with ldap backend - restarting
>> automounter with verbose logging is not too practical in the
>> production environment.
>>
>> I would imagine either some small standalone program using autofs
>> internals which would dump all (or certain specified) maps or running
>> a second instance of autofs (with some parameter) which would not
>> mount anything and just dump the maps and exits.
>>
>> Is this a completely misplaced idea or is there a way to achieve this
>> functionality now?
>
> Well, back in the autofs4 days, when way too much logic was put into the
> init script, we basically had to do this. ;-) See the --dumpmap switch
> in v4. I can see that it could be a useful aid for administrators to
> ensure that their maps look like they think they do, especially with
> nsswitch and included maps, and those pesky null maps.
Well, there you go.
This sounds like a +1 in favour to me.
Ian
next prev parent reply other threads:[~2009-11-12 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 13:21 Automounter to dump maps Ondrej Valousek
2009-11-12 13:43 ` Jeff Moyer
2009-11-12 14:58 ` Ian Kent [this message]
2009-11-12 14:52 ` Ian Kent
2009-11-12 17:08 ` Ondrej Valousek
2009-11-17 7:55 ` Ian Kent
2009-11-18 13:56 ` Ondrej Valousek
2009-11-18 14:12 ` Ian Kent
2009-11-18 14:31 ` Ondrej Valousek
2009-11-18 14:41 ` Ian Kent
2010-01-12 9:18 ` Ondrej Valousek
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=4AFC2279.6070009@themaw.net \
--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.