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: Automounter to dump maps
Date: Thu, 12 Nov 2009 18:08:05 +0100	[thread overview]
Message-ID: <4AFC40F5.80909@s3group.cz> (raw)
In-Reply-To: <4AFC212C.4010409@themaw.net>


> It's not a bad idea but I wonder how useful it really is since what is
> really useful in trying to sort out problems is the debug log output.
>
>   
I agree.  This was meant to be good for situations where you know that 
autofs works fine but say you have multiple ldap servers autofs can 
connect to and you are unsure whether all are properly synchronized. 
This way you can make sure that automounter sees the "proper" data 
immediately without having to read through the detailed debug log. Even 
with a single ldap server it is often annoying to parse the debug log 
just to make sure the data is correct.

> > 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.



So can I hope something like the --dumpmap switch will be implemented 
even in v5? :-)

Many thanks,

Ondrej

  reply	other threads:[~2009-11-12 17:08 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
2009-11-12 14:52 ` Ian Kent
2009-11-12 17:08   ` Ondrej Valousek [this message]
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=4AFC40F5.80909@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.