On 25.3.2013 11:17, Adam Tkac wrote:
On Tue, Mar 05, 2013 at 05:24:26PM +0100, Petr Spacek wrote:
>On 15.10.2012 13:10, Petr Spacek wrote:
> >On 10/09/2012 03:49 PM, Petr Spacek wrote:
> >>On 10/09/2012 01:21 PM, Adam Tkac wrote:
> >>>On Mon, Oct 08, 2012 at 04:46:54PM +0200, Petr Spacek wrot
On Tue, Mar 05, 2013 at 05:24:26PM +0100, Petr Spacek wrote:
> On 15.10.2012 13:10, Petr Spacek wrote:
> >On 10/09/2012 03:49 PM, Petr Spacek wrote:
> >>On 10/09/2012 01:21 PM, Adam Tkac wrote:
> >>>On Mon, Oct 08, 2012 at 04:46:54PM +0200, Petr Spacek wrote:
> Hello,
>
> Use auto
On 15.10.2012 13:10, Petr Spacek wrote:
On 10/09/2012 03:49 PM, Petr Spacek wrote:
On 10/09/2012 01:21 PM, Adam Tkac wrote:
On Mon, Oct 08, 2012 at 04:46:54PM +0200, Petr Spacek wrote:
Hello,
Use automatic connection management in LDAP modification code to
prevent potential deadlock
On 10/09/2012 03:49 PM, Petr Spacek wrote:
On 10/09/2012 01:21 PM, Adam Tkac wrote:
On Mon, Oct 08, 2012 at 04:46:54PM +0200, Petr Spacek wrote:
Hello,
Use automatic connection management in LDAP modification code to
prevent potential deadlock.
Without this patch the plugin wil
On 10/09/2012 01:21 PM, Adam Tkac wrote:
On Mon, Oct 08, 2012 at 04:46:54PM +0200, Petr Spacek wrote:
Hello,
Use automatic connection management in LDAP modification code to
prevent potential deadlock.
Without this patch the plugin will deadlock when modify_ldap_common()
is
On Mon, Oct 08, 2012 at 04:46:54PM +0200, Petr Spacek wrote:
> Hello,
>
> Use automatic connection management in LDAP modification code to
> prevent potential deadlock.
>
> Without this patch the plugin will deadlock when modify_ldap_common()
> is called with PTR synchronization e