[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Antw: Re: Removing Berkeley DB Log Files
- To: Douglas Duckworth <dod2014@med.cornell.edu>
- Subject: Re: Antw: Re: Removing Berkeley DB Log Files
- From: Quanah Gibson-Mount <quanah@symas.com>
- Date: Thu, 07 Sep 2017 08:14:27 -0700
- Cc: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, openldap-technical@openldap.org
- Content-disposition: inline
- In-reply-to: <WM!fb8fad46a7f7eb2095cc8186beeb9d9f0d50312aca5eb970988618f032dd62722846ff5027e415c85d6fa5179afe846a!@mailstronghold-3.zmailcloud.com>
- References: <CAAKHBKkySH++oJ3Uue2HK7P7wRVuEPyWWdSrqzxEQJFQmavYjw@mail.gmail.com> <1af444e5f795475988cdce24dd419fd8@DM5PR06MB3097.namprd06.prod.outlook.com> <CAAKHBK=Uac0x9iEz9N363hb1sgfKPEhjP_dArOH05NFDkUWXDA@mail.gmail.com> <CAAKHBKnJHcSJLn5aBpEaLsvScmGka0Jt5X02HLxsgK9+LTLDMw@mail.gmail.com> <CAAKHBKm0FKBR4BLNpy6jrszFp35Eid_J2F19MKmfS+G47EKCJA@mail.gmail.com> <59A7B20C020000A100027ADA@gwsmtp1.uni-regensburg.de> <WM!75c5f9fb628f5aad9ea35102ab95078c0fe8134ef62dc34ac30713660e915ec8559f3b5033c0a51da6e5ce4a8d64d3dc!@mailstronghold-2.zmailcloud.com> <7602201167694df5ad1515171a5a7eda@DM5PR06MB3097.namprd06.prod.outlook.com> <CAAKHBKmGGxH+0OdsDCpznCVx4uFfYLTVsQKCh8Z9tbjYQ9MUYA@mail.gmail.com> <WM!9d2cf1413621d6c2c8618759ef389442d5384a915cd9af26fa081c79a6e13fb0bb9953fd20206b49a87a76b6e254b972!@mailstronghold-1.zmailcloud.com> <2032476F3CBBE8B34FB96BAD@192.168.1.30> <59AD0FEB020000A100027B8E@gwsmtp1.uni-regensburg.de> <WM!b7a1793e73f4baff9bcc672b4f60504d172a9e65eefc442e29c9cc1036e08d30b5d92ede029130aaaad3c0fcebeacc34!@mailstronghold-1.zmailcloud.com> <6b5e19762433447da4eeebe685a7a123@DM5PR06MB3097.namprd06.prod.outlook.com> <CAAKHBK=555-+mUuA9KeGo02zhkkWNuJAJkPng0FrAaSxGi2ePA@mail.gmail.com> <CAAKHBK=4EfvEAXRDo3yuU6CXJm_3wHPCXpDv1Va7bA_owoaydQ@mail.gmail.com> <WM!e404d856b60aa820333de91dcfed92b64c964fc15fb5b7a08182caaeb445907a077d687e72d00c69ae57a4304ed8db56!@mailstronghold-1.zmailcloud.com> <77e7ae3f77b34d168b089346e85d7ca8@DM5PR06MB3097.namprd06.prod.outlook.com> <CAAKHBKmgo7WV3eVv0FyQNiGRxrVYDgAD8uef=5ibdgs=OhPfmQ@mail.gmail.com> <WM!c8eaecb81c9dbe90a64ad1f082788bd9acf5836adaee026b0745fa3fbc7787ad42172d718c21109b74cd6f59978f4065!@mailstronghold-1.zmailcloud.com> <D427EB087524F9F353C33B13@192.168.1.30> <WM!d52f1de2a2cc0cbea8b135b35c44bda6fbac42c0f6cc2f237eee60d094b1d82f0591ee83a7fd909f1fc55a1c5b4d4f92!@mailstronghold-2.zmailcloud.com> <f82c90221fce45c89de1c30c7052fb18@DM5PR06MB3097.namprd06.prod.outlook.com> <CAAKHBKnK56s0vYryR+a0YwbqqdrMWMP_Tbn8XNvPQBckep=jaQ@mail.gmail.com> <WM!fb8fad46a7f7eb2095cc8186beeb9d9f0d50312aca5eb970988618f032dd62722846ff5027e415c85d6fa5179afe846a!@mailstronghold-3.zmailcloud.com>
--On Thursday, September 07, 2017 12:03 PM -0400 Douglas Duckworth
<dod2014@med.cornell.edu> wrote:
Why would you want to rename a subtree? I can only think of a scenario
if for example we would have to sync with another LDAP cluster that
perhaps had ou=Accounts whereas we have ou=People.
A subtree is simply any DN that has children.
So if you, for example, had:
dn: uid=jdoe, cn=people, dc=example, dc=com
dn: signature=work, uid=jdoe, cn=people, dc=example, dc=com
And jdoe got divorced and changed their last name, and wanted their uid
updated, you could do a subtree rename to fix her entry and all children
entries at the same time. Otherwise, you'd have to either delete the
existing entries and create new ones, or create new ones and delete the old
ones, etc. Or stop everything, do an export, fix the data, reimport.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>