All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Valousek <webserv@s3group.com>
To: "autofs@linux.kernel.org" <autofs@linux.kernel.org>,
	Ian Kent <ikent@redhat.com>
Subject: autofs misbehaves when DNS RRs returns more ldap servers
Date: Mon, 27 Dec 2010 13:36:45 +0100	[thread overview]
Message-ID: <4D18885D.6010601@s3group.cz> (raw)


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

  Hi Ian,

I just found out that when using DNS RRs to find a suitable ldapserver to connect to, we do not handle correctly the situation where the 
multiple servers are found. We end up with something like this:

automount[2712]: find_server: trying server uri ldap://dccorka.dublin.ad.s3group.com:389 ldap://dclisaa.dublin.ad.s3group.com:389 
ldap://dcdub1.dublin.ad.s3group.com:389 ldap://dcduba.dublin.ad.s3group.com:389 ldap://dcdubb.dublin.ad.s3group.com:389 
ldap://dcpra1.dublin.ad.s3group.com:389 ldap://dcsjc1.dublin.ad.s3group.com:389 ldap://dcsjca.dublin.ad.s3group.com:389 
ldap://dcwro1.dublin.ad.s3group.com:389 ldap://dccork1.dublin.ad.s3group.com:389

Looking at the source code, this uri does not look valid to me.
Ok "man auto.master" says that LDAP_URI might contain "A space seperated list of server uris of the form <proto>://<server>[/]", but 
ldap_initialize() does not look like it actually supports this - a single server is assumed instead.

Can you clarify this?

In my case above, if connection to ldap://dccorka.dublin.ad.s3group.com:389 fails, autofs never tries the other servers in the list.

Many thanks & happy new year!

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

[-- Attachment #1.2: Type: text/html, Size: 3217 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:[~2010-12-27 12:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 12:36 Ondrej Valousek [this message]
2010-12-28  2:24 ` autofs misbehaves when DNS RRs returns more ldap servers 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

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=4D18885D.6010601@s3group.cz \
    --to=webserv@s3group.com \
    --cc=autofs@linux.kernel.org \
    --cc=ikent@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.