[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [Evolution] LDAP Auto-completion slowdown from 1.0.0 -> 1.0.1
- From: Austin Gonyou <austin coremetrics com>
- To: Chris Toshok <toshok hungry com>
- Cc: "Martin C. Messer" <marty redhat com>, evolution ximian com
- Subject: Re: [Evolution] LDAP Auto-completion slowdown from 1.0.0 -> 1.0.1
- Date: 16 Feb 2002 15:51:21 -0600
Excellent. Thanks so much!
On Fri, 2002-02-15 at 19:03, Chris Toshok wrote:
> On Fri, 2002-02-15 at 11:58, Austin Gonyou wrote:
> > I've confirmed that Evo is indeed making ldap calls and trying to
> lookup
> > from my ldap source. Does anyone have a basic setup that they would be
> > willing to share with regards to accessing LDAP on Exchange 5.5 or
> 2000?
> >
> > My current lines look like:
> > <section path="/Addressbook/Completion">
> > <entry name="uri" type="string"
> >
> value="ldap://mail.internaldomain.com:389/dc=internaldomain,dc=com??one"
> />
> > </section>
> >
> > Through tcpdump, when typing a name *not* in my address book I see one
> > request per letter typed. I just don't get the name to show up. I was
> > hoping that someone is using Evo and LDAP lookup with exchange. If
> > anyone has this info, I'd be happy if I could get a tip on this.
> >
> > is the ??one usual? What else should go there? Is there something else
> > instead I should be using for '??' ?
>
> Yes, the ??one is usual. Some people, depending on the layout of their
> server, might use ??sub. Those ?s separate the root DN
> (dc=internaldomain, dc=com), the attributes the ldap server is supposed
> to return (these aren't parsed/used by the backend, so leave that
> blank), and the search scope (one).
>
> The behavior you're seeing where there's one request per letter typed
> should be changing soon - see the bug mentioned earlier in this thread.
>
> toshok
>
> > TIA
> >
> > On Fri, 2002-02-15 at 08:02, Martin C. Messer wrote:
> > > I've just been able to upgrade to 1.0.2, and it seems the problem
> has
> > > gone away.
> > >
> > > On Fri, 2002-02-15 at 07:01, Martin C. Messer wrote:
> > > > I put it at the top, inside the <bonobo-config> stanza.
> > > >
> > > > I found that first issuing 'killev' to stop all related evo
> processes
> > > > made it easier to edit config.xmldb since bonobo continued to
> > > overwrite
> > > > any changes I made while it was still running.
> > > >
> > > > I've also realized that bug 16457
> > > > (http://bugzilla.ximian.com/show_bug.cgi?id=16457) might be a
> smart
> > > bug
> > > > to follow.
> > > >
> > > > Thanks.
> > > >
> > > > On Thu, 2002-02-14 at 19:46, Austin Gonyou wrote:
> > > > > I tried using this code with 1.0.2, and I can't even get it to
> work.
> > > > > Did you put that stuff at the top, bottom, or middle of the
> > > > > evolution/config.xmldb?
> > > > >
> > > > > On Thu, 2002-02-14 at 17:26, Martin C. Messer wrote:
> > > > > > Not sure if this is just my problem or a sign of something
> larger,
> > > but
> > > > > > since I've moved from 1.0.0 to 1.0.1 the address lookups from
> the
> > > > > > composer form have slowed from 1-2 seconds to ~15 seconds.
> > > > > >
> > > > > > I'm using the config.xmldb trick from the support.ximian.com
> KB to
> > > turn
> > > > > > on auto-completion against one of our internal LDAP servers. I
> > > went from
> > > > > > using 1.0.0 to using 1.0.1 in a matter of minutes and the
> slowdown
> > > > > > occurred immediately, so I don't believe there was a
> coincidental
> > > change
> > > > > > to the LDAP server itself that would have caused the
> performance
> > > change.
> > > > > > I don't maintain the LDAP server so I can't verify this.
> > > > > >
> > > > > > Regular address book auto-complete works the same as 1.0.0,
> nearly
> > > > > > instant lookups.
> > > > > >
> > > > > > Any pointers?
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > --
> > > > > > Martin Messer
> > > > > > Information Systems & Technologies
> > > > > > Red Hat, Inc.
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > evolution maillist - evolution ximian com
> > > > > > http://lists.ximian.com/mailman/listinfo/evolution
> > > > > --
> > > > > Austin Gonyou
> > > > > Systems Architect, CCNA
> > > > > Coremetrics, Inc.
> > > > > Phone: 512-698-7250
> > > > > email: austin coremetrics com
> > > > >
> > > > > "It is the part of a good shepherd to shear his flock, not to
> skin
> > > it."
> > > > > Latin Proverb
> > > > --
> > > > Martin Messer
> > > > Information Systems & Technologies
> > > > Red Hat, Inc.
> > > >
> > > --
> > > Martin Messer
> > > Information Systems & Technologies
> > > Red Hat, Inc.
> > --
> > Austin Gonyou
> > Systems Architect, CCNA
> > Coremetrics, Inc.
> > Phone: 512-698-7250
> > email: austin coremetrics com
> >
> > "It is the part of a good shepherd to shear his flock, not to skin
> it."
> > Latin Proverb
> >
> > _______________________________________________
> > evolution maillist - evolution ximian com
> > http://lists.ximian.com/mailman/listinfo/evolution
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin coremetrics com
"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]