From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Kent Subject: Re: Automounter to dump maps Date: Tue, 17 Nov 2009 15:55:17 +0800 Message-ID: <4B0256E5.7060702@themaw.net> References: <4AFC0BEB.3040808@s3group.cz> <4AFC212C.4010409@themaw.net> <4AFC40F5.80909@s3group.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4AFC40F5.80909@s3group.cz> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: autofs-bounces@linux.kernel.org Errors-To: autofs-bounces@linux.kernel.org To: Ondrej Valousek Cc: "autofs@linux.kernel.org" Ondrej Valousek wrote: > >> 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? :-) Maybe but this is a lot harder to do in v5. Maybe I will look at writing a separate utility but that isn't straight forward either. Not sure yet. Ian