All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <ikent@redhat.com>
To: Ondrej Valousek <webserv@s3group.com>
Cc: "autofs@linux.kernel.org" <autofs@linux.kernel.org>
Subject: Re: autofs misbehaves when DNS RRs returns more ldap servers
Date: Thu, 06 Jan 2011 22:07:44 +0800	[thread overview]
Message-ID: <1294322864.2852.3.camel@perseus> (raw)
In-Reply-To: <4D2581F0.8020607@s3group.cz>

On Thu, 2011-01-06 at 09:48 +0100, Ondrej Valousek wrote:
> On 06.01.2011 08:09, Ian Kent wrote: 
> > > LDAP_URI="ldap://server1 ldap://server2"
> > You are supposed to be able to do this.
> > 
> Ok I have found the problem. The construction above is working well,
> indeed.
> The problem is, that you call get_dc_list() directly in the while loop
> in function find_server() where its output is not parsed (normally the
> LDAP_URI config parameter is parsed fine).
> 
> I think that to fix it we would need to:
> 1. call the get_dc_list() before the main "while" loop
> 2. fix get_dc_list() so it rather than strcatting ldap uris into a
> single string returns the pure list so that we do not have to parse it
> again. This way it can be directly processed in the main while loop.
> 
> But I do not know how would it behave if we had something like this:
> LDAP_URI="ldap:///something ldap:///something_else".
> 
> Maybe two nested loops would be better - anyway I am sure you know
> where I am pointing now :-) 

Thanks for the suggestions.
I'm still on leave so things are still going slowly for now, but I'll
get to it.

> 
> Ondrej
> 
> 
> 
> ______________________________________________________________________
> The information contained in this e-mail and in any attachments is
> confidential and is designated solely for the attention of the
> intended recipient(s). If you are not an intended recipient, you must
> not use, disclose, copy, distribute or retain this e-mail or any part
> thereof. If you have received this e-mail in error, please notify the
> sender by return e-mail and delete all copies of this e-mail from your
> computer system(s). Please direct any additional queries to:
> communications@s3group.com. Thank You. Silicon and Software Systems
> Limited. Registered in Ireland no. 378073. Registered Office: Whelan
> House, South County Business Park, Leopardstown, Dublin 18 
> 
> ______________________________________________________________________
> 

  reply	other threads:[~2011-01-06 14:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 12:36 autofs misbehaves when DNS RRs returns more ldap servers Ondrej Valousek
2010-12-28  2:24 ` Ian Kent
2011-01-03 10:14   ` Ondrej Valousek
2011-01-06  7:09     ` Ian Kent
2011-01-06  8:48       ` Ondrej Valousek
2011-01-06 14:07         ` Ian Kent [this message]
2011-01-07 13:12           ` Ondrej Valousek
2011-01-11  6:32             ` Ian Kent
2011-02-02 14:40             ` Ondrej Valousek
2011-02-08  3:56               ` Ian Kent
2011-02-08  9:16                 ` Ondrej Valousek
2011-02-09  3:50                   ` Ian Kent
2011-02-09 14:57                     ` Wolfe, Allan
2011-02-09 16:40                       ` 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=1294322864.2852.3.camel@perseus \
    --to=ikent@redhat.com \
    --cc=autofs@linux.kernel.org \
    --cc=webserv@s3group.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.