[389-devel] Re: Trying to understand entryrdn.db

2017-08-04 Thread Ilias Stamatis
2017-08-04 16:03 GMT+03:00 Ludwig Krispenz : > > On 08/04/2017 02:08 PM, Ilias Stamatis wrote: > > Okay, now that I have read and understood dbscan's code, I have a few more > questions. > > 2017-08-03 10:10 GMT+03:00 Ludwig Krispenz : > > >> Hi, now that I know the context here are some more comm

[389-devel] Re: Trying to understand entryrdn.db

2017-08-04 Thread Ludwig Krispenz
On 08/04/2017 02:08 PM, Ilias Stamatis wrote: Okay, now that I have read and understood dbscan's code, I have a few more questions. 2017-08-03 10:10 GMT+03:00 Ludwig Krispenz >: Hi, now that I know the context here are some more comments. If the purpose is

[389-devel] Re: Trying to understand entryrdn.db

2017-08-04 Thread Nishan Boroian
Ok, thanks for the update. > > On Aug 4, 2017 at 08:08, mailto:stamatis.ili...@gmail.com)> > wrote: > > > > Okay, now that I have read and understood dbscan's code, I have a few more > questions. > > > > > 2017-08-03 10:10 GMT+03:00 Ludwig Krispenz (mailt

[389-devel] Re: Trying to understand entryrdn.db

2017-08-04 Thread Ilias Stamatis
Okay, now that I have read and understood dbscan's code, I have a few more questions. 2017-08-03 10:10 GMT+03:00 Ludwig Krispenz : > Hi, now that I know the context here are some more comments. > If the purpose is to create a useful ldif file, which could eventually be > used for import then for

[389-devel] Re: Trying to understand entryrdn.db

2017-08-03 Thread Nishan Boroian
Let's discuss more on it. > > On Aug 3, 2017 at 07:33, mailto:lkris...@redhat.com)> > wrote: > > > > > On 08/03/2017 12:24 PM, Ilias Stamatis wrote: > > > > > > > > > > That said, whenever you write an entry you always have seen the parent > > > and c

[389-devel] Re: Trying to understand entryrdn.db

2017-08-03 Thread Ludwig Krispenz
On 08/03/2017 12:24 PM, Ilias Stamatis wrote: That said, whenever you write an entry you always have seen the parent and could stack the dn with the parentid and createt the dn without using the entryrdn index. You even need not to keep track of all the entry rdsn/dns - only

[389-devel] Re: Trying to understand entryrdn.db

2017-08-03 Thread Ilias Stamatis
> > That said, whenever you write an entry you always have seen the parent and > could stack the dn with the parentid and createt the dn without using the > entryrdn index. > You even need not to keep track of all the entry rdsn/dns - only the ones > with children will be needed later, the presence

[389-devel] Re: Trying to understand entryrdn.db

2017-08-03 Thread Ludwig Krispenz
On 08/02/2017 09:12 PM, Mark Reynolds wrote: On 08/02/2017 02:19 PM, Ilias Stamatis wrote: I see now, thank you both very much! Follow-up: [1] Get entry from id2entry and use its ID [2] Look in entryrdn for the parent of the ID [3] Keep looking for parents, building the DN as

[389-devel] Re: Trying to understand entryrdn.db

2017-08-02 Thread Mark Reynolds
On 08/02/2017 02:19 PM, Ilias Stamatis wrote: > I see now, thank you both very much! > > Follow-up: > > [1] Get entry from id2entry and use its ID > [2] Look in entryrdn for the parent of the ID > [3] Keep looking for parents, building the DN as you go along > > > Example: > >

[389-devel] Re: Trying to understand entryrdn.db

2017-08-02 Thread Mark Reynolds
On 08/02/2017 11:49 AM, Ilias Stamatis wrote: > Hello, > > I would like some help in order to understand entryrdn.db. When I do > "dbscan -f entryrdn.db" I get something like: > > 3 > ID: 3; RDN: "ou=Groups"; NRDN: "ou=groups" > > C3 > ID: 6; RDN: "cn=Accounting Managers"; NRDN: "cn=account

[389-devel] Re: Trying to understand entryrdn.db

2017-08-02 Thread Ludwig Krispenz
Hi, I think this is a problem of dbscan, which tries to prettyprint the entryrdn index and seems to loop a bit. If you do db_dump -d a entryrdn.db you get the raw contents of the file , and you get much fewer records. Ludwig On 08/02/2017 05:49 PM, Ilias Stamatis wrote: Hello, I would l