From: Ian Kent <raven@themaw.net>
To: christof.koehler@bccms.uni-bremen.de
Cc: autofs@vger.kernel.org
Subject: Re: autofs reverts to IPv4 for multi-homed IPv6 server ?
Date: Wed, 04 May 2016 15:20:53 +0800 [thread overview]
Message-ID: <1462346453.6523.18.camel@themaw.net> (raw)
In-Reply-To: <20160503151345.GH6794@bccms.uni-bremen.de>
On Tue, 2016-05-03 at 17:13 +0200, Christof Koehler wrote:
> Hello,
>
> On Tue, May 03, 2016 at 03:58:38PM +0800, Ian Kent wrote:
> > On Mon, 2016-05-02 at 18:08 +0200, Christof Koehler wrote:
> > > We are still using NIS and actually we had the autofs map in NIS
> > > for years.
> >
> > Actually I hadn't thought about NIS and IPv6 and I haven't seen any
> > discussion about it so it probably isn't ok with IPv6.
> Still, if you need any tests ...
Right, thanks.
>
> >
> > The autofs LDAP code is complicated, it's difficult to work with.
> >
> > Anyway, for my part, if you have a system that your site is
> > comfortable
> > with that suits your needs, and you don't have a compelling reason
> > to
> > move to LDAP, I'd recommend holding back from moving to it.
>
> I believe that, especially considering that there are three (?)
> different
> schemas for storing them. That's sufficient to convince me to not
> store our
> non-executable maps in LDAP (if I ever move to LDAP). I can manage
> them
> fine using ansible I believe.
There's really only two when it comes down to it.
I get confused about the rfc designations for these.
I think rfc2307 is what I have called the NIS schema and rfc2307bis is
what I usually call, well, rfc2307bis.
The rfc 2307 rfc is a subset of rfc 2307bis so they are really just one
schema. The bis schema adds automount* attributes to the existing nis*
attributes.
One might use the nis* attribute names if coming from a NIS environment,
especially if there were conversion utilities available.
But the bis schema is preferred IMHO.
The main advantage of the bis schema is the automountKey attribute is
case sensitive, the NIS schema uses the cn attribute which IIRC is not
case sensitive.
There is another schema which I think have mistakenly called rfc 2307 in
the past but I think that one uses incorrect OID assignments so it
shouldn't be used.
Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
next prev parent reply other threads:[~2016-05-04 7:20 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 14:19 autofs reverts to IPv4 for multi-homed IPv6 server ? Christof Koehler
2016-04-08 4:46 ` Ian Kent
2016-04-08 10:10 ` Ian Kent
2016-04-08 10:14 ` Ian Kent
2016-04-08 12:25 ` Christof Koehler
2016-04-08 14:29 ` Christof Koehler
2016-04-08 15:32 ` Christof Koehler
2016-04-10 2:09 ` Ian Kent
2016-04-08 16:12 ` Christof Koehler
2016-04-08 16:15 ` Christof Koehler
2016-04-10 2:17 ` Ian Kent
2016-04-10 2:14 ` Ian Kent
2016-04-09 1:42 ` Ian Kent
2016-04-09 9:56 ` Christof Koehler
2016-04-10 2:29 ` Ian Kent
2016-04-25 4:40 ` Ian Kent
2016-04-25 15:06 ` Christof Koehler
2016-04-26 1:06 ` Ian Kent
2016-04-26 9:53 ` Ian Kent
2016-04-26 15:27 ` Christof Koehler
2016-04-27 1:54 ` Ian Kent
2016-04-27 2:27 ` Ian Kent
2016-04-27 16:52 ` Christof Koehler
2016-04-28 2:56 ` Ian Kent
2016-04-28 3:21 ` Ian Kent
2016-04-28 9:12 ` Christof Koehler
2016-04-28 9:10 ` Christof Koehler
2016-04-28 10:50 ` Ian Kent
2016-04-28 11:26 ` Christof Koehler
2016-04-28 12:40 ` Christof Koehler
2016-04-29 1:54 ` Ian Kent
2016-04-29 14:10 ` Christof Koehler
2016-04-29 14:42 ` Christof Koehler
2016-04-30 3:21 ` Ian Kent
2016-04-30 11:36 ` Christof Koehler
2016-04-30 15:15 ` Christof Koehler
2016-04-30 15:16 ` Christof Koehler
2016-05-02 6:01 ` Ian Kent
2016-05-02 16:08 ` Christof Koehler
2016-05-03 7:58 ` Ian Kent
2016-05-03 15:13 ` Christof Koehler
2016-05-04 7:20 ` Ian Kent [this message]
2016-05-04 12:38 ` Christof Koehler
2016-04-09 1:35 ` Ian Kent
2016-04-11 2:42 ` Ian Kent
2016-04-11 16:32 ` Christof Koehler
2016-04-11 16:35 ` Christof Koehler
2016-04-12 1:07 ` Ian Kent
2016-04-08 11:47 ` Christof Koehler
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=1462346453.6523.18.camel@themaw.net \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=christof.koehler@bccms.uni-bremen.de \
/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.