[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Odd ldapsearch behavior

To: Quanah Gibson-Mount <quanah@symas.com>
Subject: Re: Odd ldapsearch behavior
From: Frank Swasey <Frank.Swasey@uvm.edu>
Date: Wed, 11 Jan 2017 14:50:10 -0500 (EST)
Cc: Michael Ströder <michael@stroeder.com>, OpenLDAP Technical List <openldap-technical@openldap.org>
In-reply-to: <72D23178687E69A66C95E64C@[192.168.1.30]>
References: <alpine.OSX.2.20.1701111136480.8331@vc104198.hiz.rqh> <129513_1484156686_v0BHigBQ070477_73611521-739b-a596-164b-07bd2e575b9d@stroeder.com> <alpine.OSX.2.20.1701111317290.9679@vc104198.hiz.rqh> <WM!db6db033ad8151786c5717f78f71ae2fe7520574957e22747f2c4f68bc19b8aa1c4ed8d5d941e3dd003dee35f645e21c!@mailstronghold-1.zmailcloud.com> <72D23178687E69A66C95E64C@[192.168.1.30]>
User-agent: Alpine 2.20 (OSX 67 2015-01-07)

Today at 1:48pm, Quanah Gibson-Mount wrote:

--On Wednesday, January 11, 2017 1:18 PM -0500 Frank Swasey<Frank.Swasey@uvm.edu> wrote:

Today at 12:44pm, Michael Ströder wrote:

Out of curiosity:
What happens if you slapcat the data on your development server?


slapcat dumps the data just fine (meaning that the two attributes are not
duplicated).


If you are using cn=config, slapcat it and compare?

I let it build the cn=config when it starts, but I'm still one of themiscreants that is using slapd.conf...

My slapd.conf files are built using mustache templates with minimaldifferences... Is there a specific config option I should be looking atthat could cause the operational attributes to be duplicated in theoutput of ldapsearch but not slapcat?


 - Frank

References:
- Odd ldapsearch behavior
  - From: Frank Swasey <Frank.Swasey@uvm.edu>
- Re: Odd ldapsearch behavior
  - From: Frank Swasey <Frank.Swasey@uvm.edu>
- Re: Odd ldapsearch behavior
  - From: Quanah Gibson-Mount <quanah@symas.com>

Prev by Date: Re: Odd ldapsearch behavior
Next by Date: Re: Odd ldapsearch behavior
Index(es):
- Chronological
- Thread