[389-devel] Take 2: please review ticket 394 - error deleting a specific userpassword

[Mark Reynolds]

Added changes for the password entry extension.

 Original Message 
Subject: 	[389-devel] please review ticket 394 - error deleting a 
specific userpassword

Date:   Wed, 14 Nov 2012 15:52:47 -0500
From:   Mark Reynolds 
Reply-To: 	389 Directory server developer discussion. 
<389-devel@lists.fedoraproject.org>
To: 	389 Directory server developer discussion. 
<389-devel@lists.fedoraproject.org>




https://fedorahosted.org/389/ticket/394

https://fedorahosted.org/389/attachment/ticket/394/0001-Ticket-394-modify-delete-userpassword.patch

--
Mark Reynolds
Red Hat, Inc
mreyno...@redhat.com

--
389-devel mailing list
389-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel

--
389-devel mailing list
389-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel

Re: [389-devel] Please Review : Decreasing MAX Replication Retry time

[Rich Megginson]

On 11/18/2012 11:40 PM, Divya Ravikumar wrote:


Hi Rich,

The requirement is to minimize the replication retry time to minimum 
so that even if one of the masters in the community  goes down and 
comes up after one hour, replication happens immediately without 
manual intervention.




The default 5 minutes is too long?


Thanks,

Divya.R

*From:*Rich Megginson [mailto:rmegg...@redhat.com]
*Sent:* Friday, November 16, 2012 8:11 PM
*To:* 389 Directory server developer discussion.
*Cc:* Divya Ravikumar
*Subject:* Re: [389-devel] Please Review : Decreasing MAX Replication 
Retry time


On 11/16/2012 05:39 AM, Divya Ravikumar wrote:

converted from rtf

Hi All,

I need to reduce the max Replication retry time for my customer 
requirement



What is the requirement?


I have raised a enhancement request with fedora(Ticket 525).

As an immediate fix I have reduced the value of  
PROTOCOL_BACKOFF_MAXIMUM variable in repl5_prot_private.h from 300 
seconds to 15 seconds.


I find no impact other the max retry time limit getting reduced to 15 
seconds(which is my actual requirement) .


Does anyone see any potential flaw happening in replication due to 
this change.


Thanks in advance.

Regards,

Divya.R




--
389-devel mailing list
389-devel@lists.fedoraproject.org  
https://admin.fedoraproject.org/mailman/listinfo/389-devel



--
389-devel mailing list
389-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel

[389-devel] please review ticket 504: allow turning off name2asi and oid2asi table locks

[Ludwig Krispenz]

Please review the following fix for ticket #504

If schema modification is disabled, the access to the attribute syntax 
table can be done without locking.

In that state a client attempt to modify the scema needs to be rejected.

https://fedorahosted.org/389/ticket/504
https://fedorahosted.org/389/attachment/ticket/504/0001-Fix-for-ticket-504.patch

Regards,
Ludwig

--
389-devel mailing list
389-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel