All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Valousek <webserv@s3group.cz>
To: autofs@linux.kernel.org
Subject: Re: autofs misbehaves when DNS RRs returns more ldap	servers
Date: Wed, 09 Feb 2011 17:40:18 +0100	[thread overview]
Message-ID: <4D52C372.3010104@s3group.cz> (raw)
In-Reply-To: <AE70589A6589BA448AC7222D2428F8DE792AE7@houmsmsgexg001.anadarko.com>


[-- Attachment #1.1: Type: text/plain, Size: 2378 bytes --]

  Ok,
LDAP URI can not contain spaces, Ian was right...
Ondrej

On 09.02.2011 15:57, Wolfe, Allan wrote:
> A copy of the RFC for LDAP URI formatting can be found at
> http://www.faqs.org/rfcs/rfc2255.html it documents how the URI should be
> constructed/interpreted.
>
> -----Original Message-----
> From: autofs-bounces@linux.kernel.org
> [mailto:autofs-bounces@linux.kernel.org] On Behalf Of Ian Kent
> Sent: Tuesday, February 08, 2011 9:50 PM
> To: Ondrej Valousek
> Cc: autofs@linux.kernel.org
> Subject: Re: [autofs] autofs misbehaves when DNS RRs returns more ldap
> servers
>
> On Tue, 2011-02-08 at 10:16 +0100, Ondrej Valousek wrote:
>>> Yes, and replied on the 11/01, did you miss it?
>>>
>> Ok I must have missed it - now I see you have taken a different
>> approach - you are constructing a single looong string with all ldap
>> uris and then you parse them again.
>> I must say I do not like it too much as:
>> a) it is wasted effort (merging together and then splitting again)
>> b) potentially can ldap uri contain spaces I think
> Don't think so, in this case anyway.
>
> The uris used here aren't full uris, they can only have the proto, host
> name and port. AFAIK, host names can't have spaces in them yet.
>
>> But if you like it more, I am fine with it, too.
> Yeah, your points above are well taken but had already been done and
> committed to the repo so to change would be more work with the potential
> for mistakes.
>
> Ian
>
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
>
> Anadarko Confidentiality Notice: This electronic transmission and any
> attached documents or other writings are intended only for the person
> or entity to which it is addressed and may contain information that is
> privileged, confidential or otherwise protected from disclosure. If you
> have received this communication in error, please immediately notify
> sender by return e-mail and destroy the communication. Any disclosure,
> copying, distribution or the taking of any action concerning the contents
> of this communication or any attachments by anyone other than the
> named recipient is strictly prohibited.
>
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs


[-- Attachment #1.2: Type: text/html, Size: 3695 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs

      reply	other threads:[~2011-02-09 16:40 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
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 [this message]

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=4D52C372.3010104@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.