From: c.wegener@itcampus.de
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Directory services (was Re: [gentoo-dev] maybe it is time to put portage queries into a database.)
Date: Fri, 27 Jun 2003 17:21:02 +0200 [thread overview]
Message-ID: <20030627152102.GC1717@pbook.polysynx.foo> (raw)
In-Reply-To: <200306270758.42517.zack@tehunlose.com>
On Fri, Jun 27, 2003 at 07:58:39AM -0700, Zack Gilburd wrote:
Content-Description: signed data
> On Friday 27 June 2003 05:58 am, Rigo Ketelings wrote:
> > Op vr 27-06-2003, om 14:23 schreef Eric Sammer:
> > > Just to add something to my last email about portage and database /
> > > directory services...
> > >
> > > While talking to my wife this morning (a sysadmin and security
> > > professional and fellow gentoo user) about this situation, we realized
> > > something else about portage in openldap. This would (or could,
> > > depending on implementation) severely limit the rsync bottle neck by
> > > allowing for a hierarchy of directory servers to be replicated from by
> > > users.
> >
> > I REALLY like this idea..
>
> I /tried/ using LDAP as my authentication for pam a while back, in hopes of
> having a nice, network-wide, roaming profile. However, such hopes were
> quickly shattered once I got authentication going even locally. My login
> attempts would take /quite/ a while and it was very inefficient. I would
> rather see a MySQL database.
>
As directory services are optimized for read performance, there are
disadvantages for write access to a directory service. But compared to
the amount of user needing read access to a directory service the
number of write access updates should REALLY small.
I think your bad experience with LDAP as authentication service may
have to do with misconfiguration or lack of optimization.
> > > With clever use of referals and replication, you could
> > > effectively remove the rsync issues of bandwidth and the
> > > "stop-syncing-so-often-it's-rude" problem. Updates to portage would be
> > > propagated down the line when commited moving a smaller (but steady)
> > > stream of traffic rather than unpredictable bursts (note: that's an
> > > assumption). This would eliminate the need for 'emerge sync' (in theory).
> > >
> > > Again, this is all very academic as the data to back up these ideas is
> > > out of the public eye (thankfully). Maybe just food for thought...
> > >
> > > Thanks to all devs for all the great work.
> >
> > Yup, can't say that enough too ;)...
>
> Granted I am incorrect about my assertions above, I would like to see this
> *work* in a real-world situation before I say, "Yea, sure, let's give LDAP a
> try..."
christoph
--
^*^
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-06-27 15:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 22:00 [gentoo-dev] maybe it is time to put portage queries into a database Tony Clark
2003-06-24 22:16 ` jesse
2003-06-24 22:36 ` Tony Clark
2003-06-25 6:30 ` Sven Vermeulen
2003-06-24 22:52 ` Julien Herfurth
2003-06-24 22:36 ` Henti Smith
2003-06-24 23:04 ` jesse
2003-06-24 22:58 ` Henti Smith
2003-06-24 23:57 ` Brian Jackson
2003-06-25 3:05 ` Tony Clark
2003-06-25 3:37 ` jesse
2003-06-24 23:04 ` Tony Clark
2003-06-27 2:03 ` Mark Bainter
2003-06-27 6:45 ` Eric Sammer
2003-06-27 12:23 ` [gentoo-dev] Directory services (was Re: [gentoo-dev] maybe it is time to put portage queries into a database.) Eric Sammer
2003-06-27 12:58 ` Rigo Ketelings
2003-06-27 14:58 ` Zack Gilburd
2003-06-27 15:21 ` c.wegener [this message]
2003-06-27 15:27 ` Patrick Kursawe
2003-06-27 15:38 ` Eric Sammer
2003-06-27 15:28 ` Eric Sammer
2003-06-27 15:32 ` Patrick Kursawe
2003-06-27 15:41 ` Eric Sammer
2003-06-27 19:38 ` Paul de Vrieze
2003-06-24 22:16 ` [gentoo-dev] maybe it is time to put portage queries into a database Brian Jackson
2003-06-24 22:41 ` Tony Clark
2003-06-24 22:41 ` Marius Mauch
2003-06-24 23:14 ` kl4rk
2003-06-25 2:20 ` jesse
2003-06-25 4:08 ` Matthew Kennedy
2003-06-25 10:39 ` Paul de Vrieze
2003-06-25 11:01 ` kl4rk
2003-06-25 11:57 ` rob holland
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=20030627152102.GC1717@pbook.polysynx.foo \
--to=c.wegener@itcampus.de \
--cc=gentoo-dev@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox