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

Re: (ITS#7212) slapmodify support for back-config

Hash: SHA1

On 04/23/2012 06:06 PM, ondrej.kuznik@acision.com wrote:
> On 04/13/2012 04:00 PM, ondrej.kuznik@acision.com wrote:
>> On 03/20/2012 11:11 AM, ondrej.kuznik@acision.com wrote:
>>> For slapmodify to be usable on a database, that database needs
>>> to implement the bi_tool_dn2id_get and bi_tool_entry_modify
>>> functions, which is not the case of the back-config. I've put
>>> together a minimal (and maybe too naive) implementation of
>>> these for back-config and back-ldif at the above link.
>> Ok, nevermind for now, the implementation was too naive and
>> would break some other things (the slapadd in test005).
> I prepared an updated version of the patches below, patches
> 1-4,8-12 add this support and introduce a new testcase, temporarily
> assigned to the currently free position 007 which will ignore
> errors, if encountered during slapmodify invocation.
> ftp://ftp.openldap.org/incoming/Ondrej-Kuznik-20120423-slapmodify-support.tgz

forgot to include the IPR Notice for the above patch series:

The attached file is derived from OpenLDAP Software. All of the
modifications to OpenLDAP Software represented in the following
patch(es) were developed by Acision. Acision has not assigned rights
and/or interest in this work to any party. I, Ondrej Kuznik am
authorized by Acision, my employer, to release this work under the
following terms.

The attached modifications to OpenLDAP Software are subject to the
following notice:
Copyright 2012 Acision
Redistribution and use in source and binary forms, with or without
modification, are permitted only as authorized by the OpenLDAP Public

- --
Ondrej Kuznik
A: Because it destroys the flow of the conversation.
Q: Why is it bad?
A: No, it's bad.
Q: Should I top post in replies to mailing lists or on Usenet?
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.