Help wanted: Parse and import the LDAP display specifiers

Andrew Bartlett abartlet at
Tue Sep 1 23:03:24 MDT 2009

On Wed, 2009-09-02 at 10:24 +0530, Sreepathi Pai wrote:
> On Wed, Sep 2, 2009 at 7:57 AM, Andrew Bartlett<abartlet at> wrote:
> > I wondered if you (or someone else on the list) would like to do the
> > same with the display specifiers?
> Sure. I had a look at them at them, and they're in much better shape
> the schema files! In fact, I was wondering if:
> * commenting the license text at the top
> * possibly removing  "changetype: add" from each entry, and
> * replacing <configuration NC Distinguished Name> with ${CONFIGDN}
> would do the job? 

I think so.  And then just having that processing as part of the
provision, like the schema. 

> As far as I can tell, there are no fields which
> require pre-processing like in the AD Schema (e.g.  systemFlags or
> systemFlagsEx which had to be converted from their constant names to
> their constant values). They've used the numeric values directly here.

Excellent.  I did think it looked like an easier task. 

> I've only had a quick look and can only look at this closely over the
> weekend (sorry!). Do let me know if you try out the above and whether
> it works or not.

That would be great!

Andrew Bartlett

Andrew Bartlett                      
Authentication Developer, Samba Team 
Samba Developer, Cisco Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the samba-technical mailing list