[389-devel] [lib389] Please review: Issue 21 - Test failures due to undefined serverid attribute

https://pagure.io/lib389/issue/21 https://pagure.io/lib389/issue/raw/files/f58262938481e98e5d8d33c29e68b541e05e33e7b8d04f371a9e71aac6605c11-0001-Ticket-21-Test-failures-on-dirsrv_test.py-due-to-und.patch ___ 389-devel mailing list -- 389-devel@lists.fedo

[389-devel] Please review: [lib389] Issue 23 - Use DirSrv.exists() instead of manually checking for instance's existence

https://pagure.io/lib389/issue/23 https://pagure.io/lib389/issue/raw/files/188e95c5b473cf138a48a5f0e3946f69b13706dd02f5de128006493c031bc9f3-0001-Ticket-23-Use-DirSrv.exists-instead-of-manually-chec.patch ___ 389-devel mailing list -- 389-devel@lists.fedo

[389-devel] [lib389] dsconf plugins support and cmd line design

Hello, I'm going to add support for the memberOf plugin into the dsconf tool. However, because this is going to be the first plugin to be configurable through lib389, design decisions will affect all future plugins to be supported. I'd like thoughts on which approach would be more convenient for

[389-devel] Please review: [lib389] Issue 31 - Initial MemberOf plugin support

https://pagure.io/lib389/issue/31 https://pagure.io/lib389/issue/raw/1bd423d6be439dd1d5a1f5f15ea510f3db5966b83e78476cf327a925b9415dcd-0001-Issue-31-Initial-MemberOf-plugin-support.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To u

[389-devel] Please review: [lib389] Issue 31 - Initial MemberOf plugin support

https://pagure.io/lib389/issue/31 https://pagure.io/lib389/issue/raw/ffe425b37463aafb5ba49efffa9dd4b0a3ffd2d45bf516f21aecee4360e79dfb-0001-Issue-31-Initial-MemberOf-plugin-support.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To u

[389-devel] Please review: [lib389] Issue 31 - Initial MemberOf plugin support

https://pagure.io/lib389/issue/31 https://pagure.io/lib389/issue/raw/9f74332a0426d0eeb2fdb6c968db2162e55fadc1ed023906bbcbdd6a26a3f0bf-0001-Issue-31-Initial-MemberOf-plugin-support.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To u

[389-devel] Please review: [lib389] Issue 31 - Add functionality tests and more for MemberOf plugin

https://pagure.io/lib389/issue/31 https://pagure.io/lib389/issue/raw/d56ef441359485dc5628a1c3b45cf264b740cac154e9971f6c27fafde2f37b08-0001-Issue-31-Add-status-command-and-SkipNested-support-f.patch https://pagure.io/lib389/issue/raw/c446f117eb12ec05eb1d0b17978d36a425f97731adb4e5e4567b22c3562d676c

[389-devel] Please review: [lib389] Issue 31 - Add memberOf fix-up task

https://pagure.io/lib389/issue/31 https://pagure.io/lib389/issue/raw/7d89dc172113d0fc6e7f5bfa436b53012055d3d71a5593eeb8b286bea9d93dcc-0001-Issue31-Add-memberOf-fix-up-task.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscri

[389-devel] Please review: [lib389] Issue 67 - Add ensure_int function

https://pagure.io/lib389/issue/67 https://pagure.io/lib389/issue/raw/ec932550a7da4a9de21e8002a535b1aafd07f44eaad2ae5eeea572fde2d14c81-0001-Issue-67-Add-ensure_int-function.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscri

[389-devel] Please review: [lib389] Issue 31 - Allow complete removal of some memberOf attrs after #49284 fix

https://pagure.io/lib389/issue/31 https://pagure.io/lib389/issue/raw/9ca21074d6979ee74b3b50dc13b25257ed1486b461997606cc28938372aa2231-0001-Issue-31-Allow-complete-removal-of-some-memberOf-att.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproj

[389-devel] Beginner's questions + referint-logfile missing

Hi all, I'm kind of a C newbie and I'm trying to take a crack at fixing some things on the C codebase of DS. I've got a few really entry-level questions that I'd like to ask. 1. How can I re-compile only a single file e.g. /ldap/servers/plugins/referint/referint.c? How about re-compiling all plug

[389-devel] Please review: Issue 49314 - Add untracked files to the .gitignore

https://pagure.io/389-ds-base/issue/49314 https://pagure.io/389-ds-base/issue/raw/5d54b17b9642779fd19d96e65d7f9af0c153eaaac62397c915288c47938e6ff4-0001-Issue-49314-Add-untracked-files-to-the-.gitignore.patch ___ 389-devel mailing list -- 389-devel@lists.

[389-devel] Implementing Referential Integrity by using a queue instead of a file

Hello, A desire had been expressed to get rid of referint plugin's logfile: https://pagure.io/389-ds-base/issue/49202 It finally turns out that this file is used for other purposes than real logging. The referint plugin currently works like that; When the delay update is set to be more than 0 a

[389-devel] Please review: [lib389] Issue 74 - Advice users to set referint-update-delay to 0

https://pagure.io/lib389/issue/74 https://pagure.io/lib389/issue/raw/e8b0294326862b6eb3d3db0fa101f7e870f94523e7175a0340cccb18718227aa-0001-Issue-74-Advice-users-to-set-referint-update-delay-t.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproj

[389-devel] Please review: Issue 49315 - Log a warning whenever unauthenticated binds are enabled

https://pagure.io/389-ds-base/issue/49315 https://pagure.io/389-ds-base/issue/raw/c6f0c622a9bf124eab65e1b64d900bc5dac8fa36259e6cbcb0209e4a7a1ae3a8-0001-Issue-49315-Log-a-warning-whenever-unauthenticated-b.patch ___ 389-devel mailing list -- 389-devel@lis

[389-devel] Please review: [lib389] Issue 78 - Add exists() method to DSLdapObject

https://pagure.io/lib389/issue/78 https://pagure.io/lib389/issue/raw/c2b0f90d3cf280a4736a2f6e1a97a810734fa9b5119e1cb934ab642652e7282e-0001-Issue-78-Add-exists-method-to-DSLdapObject.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To

[389-devel] Please review: [lib389] Issue 48 - Add support for USN plugin

https://pagure.io/lib389/issue/48 https://pagure.io/lib389/issue/raw/44349b844e78b688e9633a325cadf268328f2ad22737094a45244c0dcd168641-0001-Issue-48-Add-support-for-USN-plugin.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubs

[389-devel] Please review: [lib389] Issue 49 - Add support for whoami plugin

https://pagure.io/lib389/issue/49 https://pagure.io/lib389/issue/raw/2b435210f480d1f71b2dc0529e9ab570026d1a204417a94327e57f710768e471-0001-Issue-49-Add-support-for-whoami-plugin.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To uns

[389-devel] Please review: Issue 49329 - Descriptive error msg for USN cleanup task

https://pagure.io/389-ds-base/issue/49329 https://pagure.io/389-ds-base/issue/raw/22d1ad047ade37f1209125960c213eb9ec1e8acd061cc48832edc93389731697-0001-Issue-49329-Descriptive-error-msg-for-USN-cleanup-ta.patch Thanks, ___ 389-devel mailing list -- 389-

[389-devel] Please review: Issue 49309 - syntax checking on referint's delay attr

https://pagure.io/389-ds-base/issue/49309 https://pagure.io/389-ds-base/issue/raw/files/63e4a85f884c3b84e217ff38d516e18be177c3dba4bb57d2f70e827b9a8ade59-0001-Issue-49309-syntax-checking-on-referint-s-delay-attr.patch ___ 389-devel mailing list -- 389-dev

[389-devel] referint-logchanges does nothing

Hello, referint-logchanges attribute of referint plugin serves no purpose right now; it does absolutely nothing. I found out that this has been reported in the past as well: https://pagure.io/389-ds-base/issue/48185 Do we know what it was supposed to do or what it used to do? Should we maybe re

[389-devel] Please review: Issue 48185 - Remove referint-logchanges attr from referint's config

https://pagure.io/389-ds-base/issue/48185 https://pagure.io/389-ds-base/issue/raw/files/27b2c60aa523f307bf4b7e0f6e34ee448365c15a3efac3f843be21b4a58d268a-0001-Issue-48185-Remove-referint-logchanges-attr-from-ref.patch ___ 389-devel mailing list -- 389-dev

[389-devel] Please review: [lib389] Issue 46 - dsconf support for dynamic schema reload

https://pagure.io/lib389/issue/46 https://pagure.io/lib389/issue/raw/files/ccd70a66bff42bd4ba26c074281b2e69023913785b1308798e078468f44a2df9-0001-Issue-46-dsconf-support-for-dynamic-schema-reload.patch ___ 389-devel mailing list -- 389-devel@lists.fedorap

[389-devel] Trying to understand entryrdn.db

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=accounting managers" P6 ID: 3; RDN: "ou=Groups"; NRDN: "ou=groups"

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

> > 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

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-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

[389-devel] Strategy proposal for making DB dump in LDIF format from dbscan

Hi everybody, Following Ludwig's and Mark's suggestions on how to perform a database dump in LDIF format from dbscan, I have come up with a strategy. I'm talking about ticket #47567: https://pagure.io/389-ds-base/issue/47567 I'd like to discuss this strategy and get some feedback. The general id

[389-devel] Re: Strategy proposal for making DB dump in LDIF format from dbscan

I'm sorry, I'm not sure whether the code is properly formatted so I put it here as well: https://paste.fedoraproject.org/paste/vwjZFK4icUZF4YFg44EoEw Thanks, ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to

[389-devel] Please review: [lib389] Issue 92 - display_attr() should return str not bytes in py3

https://pagure.io/lib389/issue/92 https://pagure.io/lib389/issue/raw/files/fbf7fd8ed7bac76150bd05232868bfcc78faad19638b6b7954150e710e7be9a5-0001-Issue-92-display_attr-should-return-str-not-bytes-in.patch ___ 389-devel mailing list -- 389-devel@lists.fedo

[389-devel] Please review: [lib389] Issue 45 - Add support for Rootdn Access Control plugin

https://pagure.io/lib389/issue/45 https://pagure.io/lib389/issue/raw/files/01738fb1c8b5d583b4af1564e2a6683704a3e3817169ad014f32357533660ac5-0001-Issue-45-Add-support-for-Rootdn-Access-Control-plugi.patch ___ 389-devel mailing list -- 389-devel@lists.fedo

[389-devel] Please review: [lib389] Issue 93 - Fix test cases in ctl_dbtasks_test.py

https://pagure.io/lib389/issue/93 https://pagure.io/lib389/issue/raw/files/1a03a98186d2d713fb306f28cf12837728454d20867aa618fe37392acf1c7ab9-0001-Issue-93-Fix-test-cases-in-ctl_dbtasks_test.py.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproj

[389-devel] Please review: [lib389] Issue 43 - Add dsconf support for Referential Integrity plugin

https://pagure.io/lib389/issue/43 https://pagure.io/lib389/issue/raw/files/ae71d5937a1e1a81f334b3fd5325e2781c383e95886b0a00c3d34295b339fc44-0001-Issue-43-Add-support-for-Referential-Integrity-plugi.patch ___ 389-devel mailing list -- 389-devel@lists.fedo

[389-devel] Re: Strategy proposal for making DB dump in LDIF format from dbscan

2017-08-15 9:56 GMT+03:00 William Brown : > On Fri, 2017-08-11 at 17:49 +0300, Ilias Stamatis wrote: > > Hi everybody, > > > > Following Ludwig's and Mark's suggestions on how to perform a database > dump > > in LDIF format from dbscan, I have come up with

[389-devel] Re: Strategy proposal for making DB dump in LDIF format from dbscan

2017-08-17 3:55 GMT+03:00 William Brown : > On Tue, 2017-08-15 at 22:03 +0300, Ilias Stamatis wrote: > > 2017-08-15 9:56 GMT+03:00 William Brown : > > > > > On Fri, 2017-08-11 at 17:49 +0300, Ilias Stamatis wrote: > > > > Hi everybody, > > > > >

[389-devel] Re: Strategy proposal for making DB dump in LDIF format from dbscan

parentid index is readable as well. So we depend on two files instead of one for exporting the database. Does this matter or we don't care at all? Thanks. > Ludwig > > > On 08/17/2017 02:55 AM, William Brown wrote: > > On Tue, 2017-08-15 at 22:03 +0300, Ilias Stamatis wrote: